On Jan 18, 2007, at 11:32 AM, Brad Perkins wrote:
If you can test your system with real world usage load that might give you a better idea if having too much session data will be a problem. If that shows that this might be a problem, another option would be to just store a visited page reference in your session and store the data that will allow the users to "return to the area in the same state as they left" in the database.
From what David mentions, I don't see any problem with the memory demands we may incur. While we may have more memory per web user, we will have a lot less users.
I may have been a bit simplistic with the description of "returning" as we need not only the page but also the selection of records and the search criteria.
Thanks! Jim Rietz Enterprises (630) 910-7075 <mailto:[EMAIL PROTECTED]> <http://www.think-different.com> _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
