[Catalyst] RunAfterRequest/delayed Catalyst view

2010-04-30 Thread Steve Kleiman
I posted this a while ago but I think it got lost in that tumultuous Alternatives to Catalyst melee. Figured I'd try again now that things have calmed down a bit Using Catalyst::Plugin::RunAfterRequest to handle some housekeeping after I've executed $c-detach. Works great, but... What I'd

Re: [Catalyst] RunAfterRequest/delayed Catalyst view

2010-04-30 Thread Tomas Doran
On 30 Apr 2010, at 07:00, Steve Kleiman wrote: Thanks in advance for any insights. No ideas I'm afraid. However I don't see any reason why this couldn't / shouldn't work.. Could you work up some test cases (or a very small test app) for either View::Email or ::RunAfterRequest which

Re: [Catalyst] RunAfterRequest/delayed Catalyst view

2010-04-30 Thread Devin Austin
On Fri, Apr 30, 2010 at 12:09 AM, Tomas Doran bobtf...@bobtfish.net wrote: On 30 Apr 2010, at 07:00, Steve Kleiman wrote: Thanks in advance for any insights. No ideas I'm afraid. However I don't see any reason why this couldn't / shouldn't work.. Could you work up some test cases (or a

Re: [Catalyst] RunAfterRequest/delayed Catalyst view

2010-04-30 Thread Steve Kleiman
Here goes...hopefully a simple test case for the RunAfterRequest oddness. The code below works as expected...an email is dispatched. == sub tester :Local { my ( $self, $c ) = @_; $c-stash( email ={

Re: [Catalyst] RunAfterRequest/delayed Catalyst view

2010-04-30 Thread Bill Moseley
On Fri, Apr 30, 2010 at 2:38 PM, Steve Kleiman st...@prodhub.com wrote: Here goes...hopefully a simple test case for the RunAfterRequest oddness. This is really not the response you were hoping for, but have you considered not using RunAfterRequest? I either send email directly during the

Re: [Catalyst] RunAfterRequest/delayed Catalyst view

2010-04-30 Thread Steve Kleiman
That's definitely my fallback if necessary. I really like using the Catalyst-centric option because it's easier for my brain to compartmentalize. It keeps the email dispatching process consistent with the rest of the Email::Template paradigm used throughout my app. Also it's not just for email

[Catalyst] Returning error codes to the user.

2010-04-30 Thread Bill Moseley
I have a CRUD interface to an application. This is used for both the Web and directly as an API. The model uses DBIC which, as you know, allows chaining resultsets, which I use to add additional constraints to the result set. So, a request for, say, /user/1234 might result in: $c-model(

Re: [Catalyst] RunAfterRequest/delayed Catalyst view

2010-04-30 Thread Bill Moseley
On Fri, Apr 30, 2010 at 3:59 PM, Steve Kleiman st...@prodhub.com wrote: That's definitely my fallback if necessary. I really like using the Catalyst-centric option because it's easier for my brain to compartmentalize. It keeps the email dispatching process consistent with the rest of the