[Catalyst] Session duplicate key constraints on concurrent requests

[Matthias Dietrich]

Am 10.10.2011 um 17:00 schrieb Tobias Kremer:

>> Your right ;-).
> 
> And that's almost as bad as "would of been" ... ;-)

*tired
$son is consuming too much time during the nights ;-).


Back on topic:

Am 10.10.2011 um 14:56 schrieb Tobias Kremer:

> Yes, but does that really matter? If you're using Store::Memcached for
> example, one session would overwrite the other's data, thus you'll
> loose data anyways. There's no perfect solution to this problem, I
> guess :)

That depends.  At least you'll lose(!) another request's data.  But then you'd lose the data of the second request, which may not be better.  So...  I thing Store::DBI's way seems good.

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