networked form

[leo mari]

Hi Ranchers,
May you please help me to understand this part,

Non-Networked Mode
"Architecturally, this mode must use the database and GUI from the networked form, but must not use the network server code at all"
In my design, I have two Client GUI:
______________________________
A) networked client gui
B) non networked client gui
______________________________

A) asks for hostname + port (the dbpath is choosen thru the browse button of the server gui)
B) asks for local dppath thru a browse button

Let's back to the misunderstood sentence.
How B "must use the database (!) and the GUI (!) from the networked form?
Doesn't the word "form" mean "networked client gui" ?
I think my problem is english :roll:
If so, how can I use in non networked mode, a networked db thru a networked form?
Thank you
leo

[Ashish Sarin]

The statement: "Architecturally, this mode must use the database and GUI from the networked form, but must not use the network server code at all" means that you MUST NOT have TWO client GUIs.
In Networked mode you have the following tiers: Client <----> Database Server <----> Database
In Non-Networked mode you don't use the Database server (or Network Server): Client <----> Database
So the client and database remain the same as in Networked mode but the database server code is not used.
The word 'Form' in the current context has nothing to do with 'Web Forms' or 'Forms' which are used by the end user to fill some data.
If you look at the above statement keeping in mind that in the present case 'Form' doesn't mean 'GUI' then I hope you will get the answer to your question.
regards
ashish sarin

[leo mari]

Please, tell me if I am on the right way

------------------------------networked-------------------
CLIENT (a single client program with a GUI that connects to remote database)
NETWORK SERVER (the remote server that points to db-1x1.db)
DATABASE (A data access system that provides record locking and search)
-----------------------------------------------------------

-----------------------------NON networked-----------------
CLIENT (the same client program whith the same GUI that connects to a local database)
DATABASE (A data access system that provides record locking and search)
-----------------------------------------------------------

"So the client and database remain the same as in Networked mode"

Ok

"but the database server code is not used."

Ok because I think you assumed "database server" = "Network Server"

So, in my single client GUI, must I use a JTabbedPanel, in order to provide
the choice between networked and non networked mode whitout doubling the gui?
(I cannot pass parameters from command line, all config thru the GUI)
Thanks again
leo

[Nicholas Cheung]

Hi Leo,
Your approach is ok.

Ok because I think you assumed "database server" = "Network Server"

It depends. Some people have mentioned that they prefer 2-tier system, which is what you assume. Some people have proposed that a 3-tier system is a bit more easy to develop, test, and maintain.
Personally, I feel both options are acceptable. I have chosen to develop a 3-tier system becos it fits OO more (OO becomes part of the consideration in the new assignment). Client mainly deal with clients for capturing clients' input; Network server only concerns about the network connectivity; Database server focuses on how the data is read and write from the database file.
Just pick an apporach that you feel comfortable.

So, in my single client GUI, must I use a JTabbedPanel, in order to provide
the choice between networked and non networked mode whitout doubling the gui?

For choosing the network mode (network or non-network), I dont have the JTable. I just pops up a JFrame with some textfields to capture the input (DB file location or DB server location, depends on the mode).
Once the connection has been setup, the *real* GUI with the JTable will be popped up, which is used for the booking system.
Nick.