Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring 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
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Notifying Multiple Clients

 
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello, I am new to the ranch here but have been a silent observer for some time. I have a question about the functionality of the B&S project.

It makes no mention of this in my project specs, but is it required to have some kind of network server notification from the server to the client(s) whenever one client makes a change to the database? By doing this, all clients would then be updated to reflect the latest changes to the database whenever a change occurs (updating a record or deleting a record, etc.). I have not seen anything like this in Max's book or the Exam Cram book - perhaps this is beyond the scope of this project? I don't want to get docked points for missing functionality that should be there.

Any input is appreciated. Thanks.
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Rule of thumb seems if it isn't specifically required, don't bother. I'm not. Considering the whole "this will eventually be a web app" portion of the description, server->client notification is a complete waste of effort IMO.
 
Ranch Hand
Posts: 783
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Implementing the Observer pattern is important for a real world project, but for this assignment it has generally been considered outside the scope of the project. You will not lose any points if you do not implement it.

If you do decide to implement it, realize that there are some issues using java.util.Observable with RMI... it has been brought up a few times in this forum, so you should be able to find the threads.
 
David Sham
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks a lot for your replies. If it's not required, then I'm not going to do it. One less thing to worry about, and one less thing to potentially go wrong during evaluation. Thanks again.
 
What are your superhero powers? Go ahead and try them on this tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic