This week's book giveaway is in the Cloud/Virtualization forum.
We're giving away four copies of Kubernetes in Action and have Marko Luksa on-line!
See this thread for details.
Win a copy of Kubernetes in Action this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Project reqs and a DataFacade  RSS feed

 
Ranch Hand
Posts: 77
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In re-reading my design spec there is a blurb:

...There are three key parts: (1) the server-side database with network server functionality, (2) the client-side graphical user interface, and (3) a client-side database client part that handles the networking on behalf of the user interface.


Given this, how is item 3 different from item 2??? I would think a "client side database client" would be functionality within the GUI. Apparently it isn't which is very confusing.
The best guess I have for this is that item 3 would be a Facade or DataAccessFacade. If so, how would a DataAccessFacade fit into a my current codebase:

In asking this question I'm not looking for someone to provide code, just a little direction.
Thanks
 
Ranch Hand
Posts: 2937
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator


If so, how would a DataAccessFacade fit into a my current codebase


It doesn't have to fit anywhere, -- it would be a stand-alone class and your client would use it.
Eugene.
 
author
Ranch Hand
Posts: 3252
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In my design, (3) consisted of a single class that I didn't even write myself: the rmic Connection stub.
The assessor was happy enough with it.
- Peter
 
Christian Garcia
Ranch Hand
Posts: 77
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you both for the information.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!