[Catalyst] Session duplicate key constraints on concurrent requests

Tobias Kremer tobias.kremer at gmail.com
Mon Oct 10 12:56:54 GMT 2011

On Mon, Oct 10, 2011 at 2:26 PM, Matthias Dietrich <mdietrich at cpan.org> wrote:
> 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".

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 :)

On Mon, Oct 10, 2011 at 1:53 PM, Janne Snabb <snabb at epipe.com> wrote:
> I think the browser will hold on to the session that it receives later.

That's exactly what would happen, because the browser will store only
the last cookie it received.

Due to the few responses we've received so far, I take it that
nobody's really using the DBIC backend in a medium-sized app? What's
your favorite session backend (that works in a load-balanced
environment) and handles quite a lot of traffic? :)



More information about the Catalyst mailing list