> -----Original Message----- > From: Anatole Kulick [mailto:[EMAIL PROTECTED]] > > Hi Prasad, > > Obviously you can save this info in DB, but it is overkill, > especially if > info is temporary. Maybe I have to change topic to: " How to share > temporary, continuously changing data between clients in EJB's?" > > Anatole > > >
Then it's really a question of how the data is used. If it needs to be used across a cluster, then you need a coherent cache, like Tangosol has been touting these last couple of weeks. If it's just some local cached data that doesn't need to be shared and synchronized across a cluster, then there's another idea I've been playing with: an in memory database. You could use hsql (formerly Hypersonic SQL) in its in-memory only version with a connection pool managed by the app server. Then you could save temporary data in a SQL compliant very-fast in-memory store, and retrieve it anywhere you want. If you wanted to get fancy, you might even have Entity EJBs mapped to the in-memory database, although that's probably overkill for almost any situation. Later, Jason ==========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
