Hello All. I'm currently investigating how OJB can help us. I'm very interested in the caching abilities of OJB. Especially from a multi-client point of view.
Here goes the question: how does OJB deal with caching of DB data when a DB has multiple client applications? For example, I have a database holding all my data, a web interface and a desktop interface, both connecting through JDBC. How does OJB caching on one client deal with the other client's updating of the DB? Obviously, the easiest solution to ensure data synchronization would be to turn off caching. However, caching is currently one of the big selling points of OJB, so turning it off is not very beneficial to me. Is there a system whereby a change in the database gets notified to all other clients, asking them to refresh their cashes? Eagerly looking forward to the answer ... JDG -- Jay Glanville --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
