Re: [PHP-DEV] Unmaintained SAPIs

2011-04-28 Thread Julien Pauli
All right ;-)

Johannes: Thanks for details about lighhtpd's internals.

Julien.P

2011/4/27 Johannes Schlüter johan...@schlueters.de

 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
 
 
 





Re: [PHP-DEV] Unmaintained SAPIs

2011-04-27 Thread Julien Pauli
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...

What about apache2filter SAPI ?

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




Re: [PHP-DEV] Unmaintained SAPIs

2011-04-27 Thread Johannes Schlüter
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



Re: [PHP-DEV] Unmaintained SAPIs

2011-04-24 Thread Pierre Joye
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.

2011/4/23 Johannes Schlüter johan...@schlueters.de:
 Hi,

 we have quite a few SAPIs where I expect that nobody looked at them for
 years. Anybody objects from dropping them from trunk? This brings less stuff
 to document and less confusion for users.

 I suggest dropping:

 aolserver
 caudium
 continuity
 milter
 phttpd
 pi3web
 roxen
 thttpd
 tux
 webjames

 I'm not sure about:

 apache_hooks
 apache2filter
 isapi (is FastCGI now preferred on Win?)

 That leaves:

 apache
 apache2handler
 cgi
 cli
 embed
 fpm
 litespeed
 nsapi

 johannes

 --
 PHP Internals - PHP Runtime Development Mailing List
 To unsubscribe, visit: http://www.php.net/unsub.php





-- 
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



Re: [PHP-DEV] Unmaintained SAPIs

2011-04-24 Thread Rasmus Lerdorf

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.

-Rasmus

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DEV] Unmaintained SAPIs

2011-04-24 Thread Pierre Joye
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



Re: [PHP-DEV] Unmaintained SAPIs

2011-04-23 Thread Sanford Whiteman
 isapi (is FastCGI now preferred on Win?)

Pls  don't  remove  ISAPI,  as  it  still  workswindofor  5.3  even if
deprecated. We still use it as part of third-party x64 Windows builds.

-- Sandy


-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php



[PHP-DEV] Unmaintained SAPIs

2011-04-22 Thread Johannes Schlüter

Hi,

we have quite a few SAPIs where I expect that nobody looked at them for 
years. Anybody objects from dropping them from trunk? This brings less 
stuff to document and less confusion for users.


I suggest dropping:

aolserver
caudium
continuity
milter
phttpd
pi3web
roxen
thttpd
tux
webjames

I'm not sure about:

apache_hooks
apache2filter
isapi (is FastCGI now preferred on Win?)

That leaves:

apache
apache2handler
cgi
cli
embed
fpm
litespeed
nsapi

johannes

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-DEV] Unmaintained SAPIs

2011-04-22 Thread Rasmus Lerdorf

On 4/22/11 6:08 PM, Johannes Schlüter wrote:


apache_hooks


We can drop apache_hooks as well. I think I was the only one ever to use it.

-Rasmus

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php