On Wed, 2011-04-27 at 15:36 +0200, Julien Pauli wrote: > I'm +1 with that list. > > I'd like to have some time to work on a lighttpd sapi if possible > (haven't seen lighttpd API yet). If someone got the same idea, just > tell it...
lighty's API for that is FastCGI. There is an native API, but plugging in PHP there would be bad in regards to lighty's event-based architecture. > What about apache2filter SAPI ? What what? I didn't here from people who are using or maintaining it ... so it's on the "i don't know" list. johannes > Julien.P > > 2011/4/24 Pierre Joye <pierre....@gmail.com> > 2011/4/24 Rasmus Lerdorf <ras...@lerdorf.com>: > > On 4/24/11 4:41 AM, Pierre Joye wrote: > >> > >> hi, > >> > >> Do we really need apache 1.x SAPIs? > >> > >> ISAPI should be kept in (was decided so by the 5.3.0 > release time), it > >> is still used and works for users with custom versions. A > new version > >> may come as well, as part of one of some features I'm > working on. > > > > Your argument for ISAPI applies exactly to Apache 1 as well. > > > Not that it is so important (does not hurt anyone to keep it > in) but > apache 1.x is dead, not IIS :). > > Cheers, > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org > > -- > > > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
