[Catalyst] Session handling under heavy usage

[apv]

On Wednesday, March 22, 2006, at 10:30  AM, Yuval Kogman wrote:
> The probability that two simultanous requests will both want to
> *write* to the session data is low, so that's why this locking crap
> hasn't been done yet (it's slow and hard).

Oh... that is not so good and comes as a bit of a shock to hear you say 
it
since I've been admiring your work on Catalyst for a long time. The 
probability
of race conditions in any kind of read/write system is very low but 
since
it absolutely will happen given enough time, locking is mandatory for
anything that could be considered professional. Or else it should have
a big note in the BUGS which says:

"May infrequently drop, erase, or corrupt your session data at seemingly
random, and impossible to predict intervals."


Your fan (and fan of safe data),
-Ashley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 855 bytes
Desc: not available
Url : http://lists.rawmode.org/pipermail/catalyst/attachments/20060322/311dbe57/attachment.bin