What am I missing here? First, the directions state, "The program must allow the user to specify the location of the database, and it must also accept an indication that a local database is to be used, in which case, the networking must be bypassed entirely." Later on, the directions say, "Your programs must not require use of command line arguments other than the single mode flag, which must be supported. Your programs must not require use of command line property specifications. All configuration must be done via a GUI, and must be persistent between runs of the program. The mode flag must be either "server", indicating the server program must run, "alone", indicating standalone mode, or left out entirely, in which case the network client and GUI must run." Here's my conclusion on what this all means: "server" - server starts, that's pretty clear. "alone" - GUI starts and only local database connections are allowed. no parameter - GUI starts and only remote database connections are allowed. At first, I was thinking that the user could ("must" be allowed to even??) change the mode between local/remote through the GUI, but I hope I'm wrong. Any thoughts?
I'm still a little confused on this. The command line is supposed to determine whether to run in "server" or "alone" mode, but the user must also be able to specify the database location in the GUI. What if program is run with command line arg of "server", but user specifies the local database via the GUI. Spec says networking must be bypassed if local database is used. 1. Wouldn't this situation be a "mode switch" from the originally selected "server" mode? 2. Followup question - Am I understanding the requirements correctly in thinking that any database that the user specifies will have to be saved in the properties file and displayed in subsequent runs of the program as a potential database selection? (i.e. persistent configuration) Thanks in advance for the help. TJ
SCJP, SCJD, SCWCD, SCBCD
Joined: Jun 02, 2003
Hi, Welcome to this forum.
What if program is run with command line arg of "server", but user specifies the local database via the GUI. Spec says networking must be bypassed if local database is used.
It's not a question of "local database file" vs "remote database file". There is a (or are some) database file(s) on the system, period. A file choosen by the server user (let's say some administrator) de facto becomes a "remote database file", while any file (even the same physical one) being choosen by a "stand-alone-mode" user de facto becomes a "local database file". Of course, stand-alone users are not supposed to choose the same physical file as the server one, while the server is running ... (See this thread). Best, Phil. PS: Your displayed name does not follow JavaRanch's naming policy. Thank you to change it here. [ October 24, 2003: Message edited by: Philippe Maquet ]
Joined: Oct 18, 2003
Thanks Phil. I fixed my name. I found another thread dealing with properties files and GUI's on the server side: NX:Some Questions(URLyBird1.3.2) Ugh, I'm still in "Concept Development" and a bit overwhelmed by all the work ahead of me. Anyway, does my understanding sound right: Server side needs a GUI to do 1. server setting (pick db file, RMI port) and save to prop file 2. start RMI server 3. stop RMI server Client side GUI will: 1. pick Remote IP and Port if in server mode and save to prop file 2. pick Database file name if in standalone mode and save to prop file If client command line says server mode, user can't pick database file name to "switch" to standalone mode. They would only be given the option of picking the Remote IP and Port Feedback very appreciated. TJ
Joined: Jun 02, 2003
Feedback very appreciated.
Sorry for the very short feedback, but as it's seems perfect ... Best, Phil.