On Thu, 2005-12-08 at 12:17 -0500, Justin Cook wrote:
> I'm not sure if I need locking or not. I think I figured out why my
> page request was hanging(due to passing session args in a component call
> - ie <& 'comp.mas', $arg => $m->session->{arg} &>), but should I still
> turn off locking completely? Is it dependent on how busy the site is
> whether or not to have locking turned on?
It is dependent on how you use the session. If you don't use locking,
you get a basic "last save wins" scenario, which can lead to lost
updates. That's what locking is intended to prevent. Some applications
are sequential enough that this is unlikely, or have very short-term use
of the data and don't care much about losing an update. If you're not
sure, use locking.
> Could this reference not going out of scope be the session parameter
> being used in a component(in the page being requested) call by chance?
It certainly looks like that is keeping the session object around for
some reason.
- Perrin
-------------------------------------------------------
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
