Hi!
Your question is close to my last and I'm not clear at all because I'm
new to mason and webapps too.
So why is the session always on a persistent layer (in
file/database/etc) and not in memory of mason/perl like a normal hash?
And whats the connection of the real session (tags in url/cookie) with
this memory area?
Whats the clue with the session and the masonallowglobal?
thx for help.
regards chris
Matt Grommes wrote:
I'm new to using MasonX::Request::WithApacheSession for sessions so
I'm wondering what people's experiences are with how much data you can
put into that session without bogging things down? I'd like to put a
potentially large (100-200+) array of numbers in a session so I don't
have to pull the data out of the database all over the site, is that
asking for trouble or am I being overly cautious?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
