This week's book giveaway is in the Agile and Other Processes forum.
We're giving away four copies of The Little Book of Impediments (e-book only) and have Tom Perry on-line!
See this thread for details.
Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

a client-side database client

 
Garandi Garandi
Ranch Hand
Posts: 192
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Architecturally, the application is a traditional client-server system. There are three key parts: the server-side database with network server functionality, the client-side graphical user interface, and
a client-side database client part that handles the networking on behalf of the user interface.

Could anyone explain the quated part.
Thank you
Garandi
[ July 02, 2003: Message edited by: Garandi Garandi ]
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 12014
220
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Garandi
I believe that this is telling you that your GUI application should not be handling networking issues within it's own code - all networking issues should be handled in the "part that handles the networking on behalf of the user interface."
To give you an example of how this applies: one class within your GUI client has to handle receiving the results of your find query. If that class is doing different work based on whether it is in networked mode or local mode then you have not made a clear separation between the two. Likewise if your class on the GUI side is handling RemoteException, then you do not have clear separation.
This might be a hint to use a facade or a factory in your GUI to connect to the database.
By the way, this does not mean that you are making three distinct applications - the networking code will be packaged with the gui code to make the overall GUI application. But it does mean that the GUI code should not have any dependency on the networking code - you should be able to pull it out, or replace it with a different networking paradigm without your GUI application noticing.
To try and explain this a different way: Speakers for your PC (if you have them) are considered part of the system, but they can be removed and the PC will still work, or they can be replaced and the PC will not be affected.
Regards, Andrew
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic