[MTOS-dev] Experimental Dispatcher

Timothy Appnel tim at appnel.com
Tue Feb 5 12:18:02 PST 2008


On 2/4/08, Reed A. Cartwright <reed at scit.us> wrote:

> Who says that 5.0 can't follow 4.1?  If anything, the prototype proves
> that it can be included as an experimental feature in the 4.x branch,
> then it can be turned into the primary feature in 5.0.

I'm all for a dispatcher and things we've been talking about, but
going straight to 5.0 seems rather ambitious and premature. I think
that is a lot to tackle, but doing it in one big overhaul would be
problematic. Its more a matter of putting these ideas out on the table
and then making a plan to get from point A to B most effectively.

> > * How would this impact MT's set of prerequisites. Does it help reduce the
> > amount of software required we need to bundle with the core? Does it
> > increase it? Does it required compiled modules?
>
> Probably increases it.  The important modules in my prototype are
> CGI::Application, CGI::Application::Dispatch, and FCGI::Engine.  I have
> no feel for these things, but CGI::Application may be a common thing on
> hosting systems, CGI::Application::Dispatch can be placed in extlibs
> with little problem, but FCGI::Engine will be more difficult.

CGI::Application has virtually no dependencies. The one that comes to
mind is HTML::Template, but that an be easily overwritten which is why
I don't quite agree with it being a requirement.

There has to be some balance here, but I don't see more (external)
dependencies being a problem if it reduces the overall amount of code.
Some modules go a bit nuts with their dependencies that we'll need to
consider what to do because we don't users to have to install all of
CPAN either.

Perhaps the FCGIEngine should be a plugin of sorts. Also, assuming
FCGI is for expert handlers, perhaps looking at modules like Ricardo
Signes CGI::Application::Server as another option.

> for me to improve its compatibility with MT.  It has a lot of
> dependencies though.  I think it might be best to require it as an
> optional dependency.  If people want to use fastcgi, they can install it.

That sounds like a reasonable way of approaching it when MTOS is ready for it.

<tim/>

-- 
Timothy Appnel
Appnel Solutions
http://appnel.com/


More information about the MTOS-dev mailing list