On Mon, Oct 10, 2011 at 2:26 PM, Matthias Dietrich <[email protected]> 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 <[email protected]> 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? :) Thanks! --Toby _______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
