http://db.apache.org/ojb/howto-work-with-clustering.html
> -----Original Message----- > From: Andrew Clute [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 29, 2003 5:09 PM > To: OJB Users List > Subject: Single cache across multiple web applications? > > > As we are moving forward in trying to standardize our > Business Domain Model, > the prevailing thought is to have a central 'Core' framework > that includes > our BusinessObjects and using OJB. > > So, we have a collection of BO's that can be used across lots > of different > disparate web applications, and the goal is to have all of the web > applications 'feeding' off one cache -- with the benefits > being obviously > cached objects, and data being fed across all of the web applications > instantly. > > However, in my test, and this does makes sense, every web > application you > create that uses OJB created it's own cache collection, with it's own > reference to objects. So, obviously, any changes made in one > web app's cache > will not be apparent in the other's cache, unless the second > app goes to the > database -- thus removing the benefit of using the cache. > > As anyone else dealt with this type of scenario? > > The immediate answer to me is to create a single application > that is the > DataService that holds the cached objects, and handles the the OJB > interface, and returns to any of the calling web applications > a reference to > the business object. Or, is this a good use of some EJB's to > transfer these > objects back and forth -- but then don't I have to worry > about my client > applications using a 'copy' of the original data-object, and > changes made to > the original cached objects will not be populated to the > client applications > -- seems like a breeding ground for out-of-sync errors. > > Sorry, if this seems to be a novice question, but I can't > seem to get my > head wrapped around a best practice for this type of scenario. > > Thanks! > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
