[Catalyst] Session duplicate key constraints on concurrent requests

[Matthias Dietrich]

Hi,

Am 10.10.2011 um 10:42 schrieb Tobias Kremer:

> a) Try to find the session, e.g. $self->model->find({ $self->id_field => $key })
> b) If found, use this session because it's still valid.
> c) If not found, create() an entirely NEW(!) session, with a new
> session-ID and insert it.

wouldn't that result in two new sessions?  Your first request would create "session:new1" and the second "session:new2", so you'll end up loosing info from "session:new1".

Matthias

-- 
rainboxx Software Engineering
Matthias Dietrich

rainboxx Matthias Dietrich   |  Phone: +49 7141 / 2 39 14 71
Königsallee 43               |  Fax  : +49 3222 / 1 47 63 00 
71638 Ludwigsburg            |  Mobil: +49  151 / 50 60 78 64
                             |  WWW  :  http://www.rainboxx.de

CPAN: http://search.cpan.org/~mdietrich/
XING: https://www.xing.com/profile/Matthias_Dietrich18
GULP: http://www.gulp.de/profil/rainboxx.html