hi @ all.
I'm not only new to mason, also new to web applications (a little bit :).
so I'm confused about the names and sense.
my mind about sessions is:
I have a global memory in my web-appl-server which is accessable over
all (the session hash (?)).
With Url/hidden field/cookie I can put hint IDs in my application that
identifies items in my global memory (shotcuts to bigger
elements - database handler, file handler, files, whatever..... ). I
can also pass parameters etc. pith url/hfields but thats not the problem.
is this point of view wrong?
I got confused after reading the configuration possibility of the
session handly with cookies. in my mind the cookie is with the
user - how to store the big data there?
is $session not the big global memory where I can do pooling of database
handles etc.?
thanks for help.
chris
-------------------------------------------------------
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
