Win a copy of 97 Things Every Java Programmer Should Know this week in the Java in General forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

clarification of requirement

 
Ranch Hand
Posts: 126
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In the description about the overall architecture, it says the system consists of 3 key parts:server-side DB, client-side GUI, and "a client-side database client part that handles the networking on behalf of the user interface". What does this third part mean? I have been thinking that the client side is just a GUI which collects information and send to the server and then display whatever received from the server. But what this means or my understanding is too simple at all?
Thanks!
 
Ranch Hand
Posts: 3451
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've had the same question come to mind. At first it sounds like a 3-tier application (GUI client, business logic, and database server) but the books on certification that I've read all indicate a 2-tier design is OK with GUI client and business logic integrated. Besides 3-tier design although easier to maintain and scale is much more difficult to design and implement.
Unless someone suggests otherwise, I'm pursuing a 2-tier solution.
 
Ranch Hand
Posts: 854
3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I suspect that the idea is that within the Client application you should separate the GUI from the part that accesses the database - not only is this a good design, but it enables you to support talking to the server-side DB *or* the local copy of the DB.
If the GUI talks directly to the server-side DB then it gets really ugly when you have to support the local version too.

Originally posted by Cathy Young:
In the description about the overall architecture, it says the system consists of 3 key parts:server-side DB, client-side GUI, and "a client-side database client part that handles the networking on behalf of the user interface". What does this third part mean?

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The third part or client side db client is the interface to the database. You have two methods of getting to the db.db file, either going through a server over a network or accessing the file locally. The client allows you to hide how you are getting there from the gui client. The gui only wants the information and doesn't care how it gets it.
Atleast this is my thoughts.
Travis Zimmerman
 
Cathy Young
Ranch Hand
Posts: 126
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks, guys. It makes sense.
 
That feels good. Thanks. Here's a tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic