plugins; was Re: [Catalyst] debug mode

[Matt S Trout]

On Wed, Jun 06, 2007 at 12:29:12PM -0700, mla wrote:
> Matt S Trout wrote:
> >On Tue, Jun 05, 2007 at 01:42:42PM -0700, Michael Reece wrote:
> >>>> sub _ACTION : Pricvate {
> >>>>   my ($self, $c) = @_;
> >>>>   $self->_context($c);
> >>>>   $self->SUPER::_ACTION($c);
> >>>> }
> >>>That's not only in the wrong place to work for begin/end/auto it  
> >>>screws up
> >>>the destruction process and is therefore really really dangerous.
> >>i had a feeling it was less than ideal, which is why i threw it out  
> >>there.  can you clarify what you mean about the destruction process?   
> >>i don't see anything special in ACCEPT_CONTEXT.pm to deal with that..
> 
> Is it not possible to offer the current Catalyst instance through
> a class method? Something analogous to Apache->request, rather than
> having to do the whole ACCEPT_CONTEXT prototype object thing?

Not without limiting ourselves in terms of planned future features. Jifty
does this because they're explicitly one app per process. We aren't.

-- 
      Matt S Trout       Need help with your Catalyst or DBIx::Class project?
   Technical Director    Want a managed development or deployment platform?
 Shadowcat Systems Ltd.  Contact mst (at) shadowcatsystems.co.uk for a quote
http://chainsawblues.vox.com/             http://www.shadowcatsystems.co.uk/