Thanks so much! I'm surprised this hasn't come up more often, as it
seems such a common thing
for an application to allow for. FWIW, I think this would make an
excellent tutorial, perhaps for
next advent calendar, or even the next Catalyst book! :-)
On 8/4/2010 3:09 PM, Bill Moseley wrote:
On Wed, Aug 4, 2010 at 11:22 AM, Steve wrote:
> Original post:
> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/msg01222.html
>
> My apologies for rehashing this old post, but this is such a *nice* thing
> to do for users that
> I'm sort of surprised the solution hasn't been implemented a
Original post:
http://www.mail-archive.com/catalyst@lists.scsys.co.uk/msg01222.html
My apologies for rehashing this old post, but this is such a *nice*
thing to do for users that
I'm sort of surprised the solution hasn't been implemented as a plugin
or something, at least
so far as I can tell
On Fri, Jan 11, 2008 at 07:06:17PM +, Jonas Alves wrote:
> On Jan 11, 2008 6:27 PM, Matt S Trout <[EMAIL PROTECTED]> wrote:
> > Don't try and serialize $c->req, just dump any POST data back out into
> > hidden fields in the login form, don't change the URL, and have the login
> > form processed
On Jan 11, 2008 6:27 PM, Matt S Trout <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 08, 2008 at 02:58:17PM -0500, [EMAIL PROTECTED] wrote:
> > Hi,
> > in my application, if a client issues a request after say 30 minutes of
> > inactivity, I want to answer his request only after successfull
> > authentic
On Tue, Jan 08, 2008 at 02:58:17PM -0500, [EMAIL PROTECTED] wrote:
> Hi,
> in my application, if a client issues a request after say 30 minutes of
> inactivity, I want to answer his request only after successfull
> authentication.
>
> Ideally, I would simply serialize $c->request in the session,
> Just a stupid thought...having not look at continuation...
> What if $c->request have freeze/thaw hooks?
... and a way to tell catalyst to unwind processing and start over with the
thawed request.
--
Julien Gervais-Bird
___
List: Catalyst@lists.scsys
[EMAIL PROTECTED] wrote:
>> Catalyst::Plugin::Continuation should do that. But it appears to be
>> broken with the current Catalyst version. Or at least I was not able
>> to make it work.
>
> Catalyst::Plugin::Continuation would have been perfect (it even has a test
> case that suits my needs:
>
> Catalyst::Plugin::Continuation should do that. But it appears to be
> broken with the current Catalyst version. Or at least I was not able
> to make it work.
Catalyst::Plugin::Continuation would have been perfect (it even has a test
case that suits my needs:
http://search.cpan.org/src/NUFFIN/C
On Jan 8, 2008 7:58 PM, <[EMAIL PROTECTED]> wrote:
> Hi,
> in my application, if a client issues a request after say 30 minutes of
> inactivity, I want to answer his request only after successfull
> authentication.
>
> Ideally, I would simply serialize $c->request in the session, ask for
> authent
Hi,
in my application, if a client issues a request after say 30 minutes of
inactivity, I want to answer his request only after successfull
authentication.
Ideally, I would simply serialize $c->request in the session, ask for
authentication, then if successfull restore the stored request to $c
11 matches
Mail list logo
