Jim,
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.
-- Brad Perkins
Jim Rietz wrote:
We are making some nice process on our first A4D project... but, we
have a question about storing collections and other things in the
user's session.
Currently, we are storing data (for the duration of the session) for
each area (page) the user goes to so when they return to the area it
is in the same state as they left. Right now, we only have 3 areas and
for each user the Active 4D Session Monitor shows around 3,600 in the
size column. There was just over 1900 after login, and each area is
adding approximately 500.
The web access will be for the sales team (25 or so) only.
I can't see any outstanding issues watching the Runtime explorer and
the web access is pretty snappy, considering we are only testing over
cable. The production project would have better internet access for
serving.
Is what we are doing something common or are we going down the wrong
road?
Thanks!
Jim
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
