Hi Richard, thanks for your reply. The one problem I can see with that is when do I remove the data from the visit object? Now I know that there's probably a way to know when a person changes pages. but what if they just close the browser? you can imagine that the amount of information is very large and there is a very large amount of users viewing the same large amount of data regularly which means that waiting for the session to time out to free the memory will probably be problematic.
On Tue, 2006-01-10 at 09:50 -0800, Richard Clark wrote: > Hi Brian, > > How about passing the data in the Visit? Or if it's so large that > the resulting HTTPSession will be too big, keep it in a database (or > some in-memory data source) and pass just the key(s) for the data > from the first page to the report generator? > > ...Richard > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Brian Sperryn Software Developer SECPay Technical Support --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
