Persisting session data outside of the httpsession

towny · **Joined:** Wed Mar 17, 2004 7:59 am **Posts:** 24

Please can you advise on the best appraoch to take:

I have a large web application, which will capture 300+ data items per session (3000+ sessions per day). I'd like to avoid holding the data in the http session as it needs to be persisted. However I have a few queries:

1) Storing it as a clob seems the most appropriate method, but this may have a trade off in that the whole clob will have to be updated for even the slightest change in data. I'm assuming that holding the data in a massive table would resolve the update problem, however there is a trade off in reading that volume of data/storing 300 rows in one hit.

2) I'm confused how caching works, is data only cahed in relation to the session that created it (i.e. requiring disconnect/reconnect) or does caching work accross sessions?

emmanuel · **Posted:** Thu Mar 25, 2004 6:37 pm

towny wrote:

Please can you advise on the best appraoch to take:

I have a large web application, which will capture 300+ data items per session (3000+ sessions per day). I'd like to avoid holding the data in the http session as it needs to be persisted. However I have a few queries:

1) Storing it as a clob seems the most appropriate method, but this may have a trade off in that the whole clob will have to be updated for even the slightest change in data. I'm assuming that holding the data in a massive table would resolve the update problem, however there is a trade off in reading that volume of data/storing 300 rows in one hit.

Are you sure clobs is your only way. Can't you map it in a more appropriate structure

towny wrote:

2) I'm confused how caching works, is data only cahed in relation to the session that created it (i.e. requiring disconnect/reconnect) or does caching work accross sessions?

You can use the second level cache for cross-session caching.