On Thu, Dec 11, 2008 at 12:04 PM, Sergio Salvi sergio.li...@salvi.ca wrote:
On Thu, Nov 20, 2008 at 4:49 PM, Tobias Kremer l...@funkreich.de wrote:
On 20.11.2008, at 21:16, Sergio Salvi wrote:
I still think the final solution (besides finding a way to make
find_or_create() atomic
On Thu, Nov 20, 2008 at 4:49 PM, Tobias Kremer l...@funkreich.de wrote:
On 20.11.2008, at 21:16, Sergio Salvi wrote:
I still think the final solution (besides finding a way to make
find_or_create() atomic), is to store flash data the session row
(either on the same column of session
of 4.009 says this bug has been fixed, so you could
try 4.010:
* Fix to re-enable TAKE_IMP_DATA_VERSION. Still have to ensure DBI
version 1.607 or higher
But I haven't tried this version yet. 4.006 works fine for me and at
that time, the latest was 4.008 so I went back to 4.006.
Sergio Salvi
(besides finding a way to make
find_or_create() atomic), is to store flash data the session row
(either on the same column of session or on a new, dedicated column).
I could try coming up with a patch + tests for this. Thoughts?
Thanks,
Sergio Salvi
On Wed, Sep 10, 2008 at 6:59 PM, Sergio Salvi [EMAIL PROTECTED] wrote:
There is a race condition in C::P::Session when using
C::Engine::Apache (and probably other engines too):
I have a simple controller action (let's call it /save) that gets data
submitted from an HTML form via POST, process
to call the Engine's finalize() method *last*,
after every other finalize() has been called?
I think that would be the safest way to fix this problem. It is
probably related to C3 MRO, but I'm not sure how to approach this
within Catalyst.
Thank you!
Sergio Salvi
PS: My environment is:
Debian 4.0
