Can Someone Explain To Me What This Means?

[Daniel Simpson]

My doc says:

The operating mode is selected using the single command line argument that is permitted. Architecturally, this mode must use the database and GUI from the networked form, but must not use the network server code at all.

When it says, Architecturally, this mode must use the database and GUI from the networked form, but must not use the network server code at all, what exactly does that mean? Can someone give me some examples of incorrect implementations that would result in an automatic failure? I want to make sure I am on the right track with this. In my controller class in my gui, I have a part (similar to Max's book) where it dynamically sets the local or network connection. I need help with the terms. In local mode I have a class that has-a Data object and provides the business methods book and search and hide data's details and calls on data's method without exposing implementation. This is a Facade, correct? So in local mode, is their such thing as a thin or fat client? Or is my local implementation just referred to as a facade? If so, then it would be wrong to name my class LocalDBAdapter, correct?Thanks!
[ January 13, 2005: Message edited by: Daniel Simpson ]

[peter wooster]

I provided a design in your "Local Adapter Issue" thread.

Using that design here's how it works:

------ Stand alone mode (arg=alone) ------------

- BookingModel has a DBAccess instance that is a Data object
- Data has a DatabaseFile singleton that does the I/O

no networking is involved

------ Networked client mode (arg="") ----------

- BookingModel has a DBAccess instance that is a DataProxy object
- DataProxy has a DataAdapter instance that is a remote DataAdapterImpl object
- DataAdapterImpl has a DBAccess instance that is a Data object
- Data has a DatabaseFile singleto that does the I/O

RMI networking is used between the DataProxy and the DataAdapterImpl. The DataProxy used a DataAdapterFactory to get the DataAdapter. DataAdapterFactoryImpl was registered in the RMI registry.

A simple factory method pattern is used to build either a Data or DataProxy depending on the startup parameter. Since both Data and DataProxy implement DBAccess this is possible.