Re: [cgiapp] Re: Yet another callback system proposal

[Michael Graham <suppressed>]

> looks like i'm way late to this discussion, but I wanted to let you know
> that I've been using WWW::Pipeline quite successfully as the framework
> for our CMS, www.enterity.com/osiris, for some months now. And having
> set up a very CGI::App-like environment via the RunMode plugin and
> friends, I've found development to be very similar to working in
> CGI::Application.

WWW::Pipeline looks interesting.  A question: how hard would it be to
use CGI::Application::Plugin modules in a WWW::Pipeline application?

Not that I have any plans to switch, but it does seem to me that as
more and more web platforms appear, it becomes harder to reuse common
modules (and right now, CGI::Application has a rich set of these).

> I've recently been toying with a caching plugin that
> intervenes 'EARLY'  in the GenerateResponse phase, and have been pretty
> happy with the limited stages.  To be honest this is actually the first
> time I've used anything other than the default MIDDLE stage.

Yeah - I think my earlier ideas regarding complicated position ordering
were misguided.  I think our current approach of having no positions is
the way to go for not.


Michael


-----------------------------------------------------------------------
Michael Graham <suppressed>

YAPC::NA 2005 Toronto - http://www.yapc.org/America/ - suppressed
-----------------------------------------------------------------------


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed