This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I'm assuming you are asking a question about how you keep two views of the same data synchronized between two clients? Am I right? If you are, then the simple answer is you don't even try. If you need this sort of functionality you need a more sophisticated client than a simple web app, which will have to constantly poll the application to keep the view roughly up to date - and this is really bad design, since you will be flooding the server with largely unneccessary requests. What is better is to assume the client's view of data can be out of date, use an optimistic locking pattern inside a transaction when a client needs to manipulate the data.
Joined: Dec 15, 2002
hi, cluck and saj... Thanks for your replies ... I guess you are right. for now, i'll think it over and discuss with you guys later. jia