> I think routing is an Apache task that's why I thought about an Apache
> module even if a PHP extension could make the trip.
>
> Other opinions ?
>
> J.Pauli
>
>
> On Tue, Jan 19, 2010 at 2:53 PM, Andreas Baumgart <ab@polycast.de
> <mailto:ab@polycast.de>> wrote:
>
> I'm not exactly familiar with Apache API internals and C but
> wouldn't it make more sense to implement this as a PHP extension
> instead? Especially considering portability. As extension are also
> written in C you can still gain the extra speed.
>
>
> On 19.01.2010, at 14:06, Julien Pauli wrote:
>
> > Hi ;-)
> >
> > We all know that making the route decision from C code (Apache)
> to PHP code (ZF router) is bad for performances.
> > I don't have measures, but IMHO , ZF routing is at least 20% less
> efficiant than Apache's C-written one (one again, I dont have
> references, but if someone does, just share them )
> >
> > I already pinged Matthew about developping an Apache module which
> could be added routes like ZF's router behavior, and populates
> $_SERVER['module'] , $_SERVER['ctrl'] and $_SERVER['action'] (for
> example).
> >
> > A friend of mine, Jerome Renard, has already developped something
> similar ; let's see http://code.google.com/p/modurlalias/.
> > The goals are mainly the sames, and by rewriting some parts of
> this code, we could have something cool.
> >
> > Are there any C skilled dev in the place (with Apache modules
> exeperience could be great) ?
> >
> > Anyway I'm gonna work on that idea for my own, so ping me if
> interrested.
> >
> > J.Pauli
>
>
Writing an apache module restricts the routing capabilities IMO,
nginx/lighttpd/cherokee etc usage is on the increase (quite dramatically
- see netcraft for details on that) so I think it would be better served
as a PHP module if it can provide, equal/similar performance benefits to
that of an apache module, it then is far less restrictive and much more
likely to be adopted.
---
Nick
没有评论:
发表评论