Hi Johannes,
Derick just copied it on the CVS server to php-src/sapi/litespeed and
gave you karma, please make a checkout of the PHP tree and test if all
works, then do a cvs rm on the old files in PECL so that's cleaned.
That's great! Thanks for the update.
Checkout a copy of
Hi George,
On Tue, 2008-04-08 at 10:12 -0400, George Wang wrote:
Either a symlink or moving the directory physically to where other SAPI
code are should work. I can check in the code to a different location if
need.
Please let me know if anything I can help. :-)
Derick just copied it on
Hi Johannes,
Well, the idea is that all PHP-specific code is licensed under the same
license terms. PCRE and GD are external libraries which live outside
PHP's context and which are simply bundled. That's why the clear
preference there is PHP License.
I have updated the license to have it
Hi Pierre,
I also prefer BSD license as well, Johannes will make the final call, if
he think that it is a show stopper, I will dual-license it.
I have updated lsapi_main.c to address the { } after an if statement
issue on the other day. If there is anything need to be taken care,
please
Hi Johannes,
Thank you for the quick reply.
Well, the idea is that all PHP-specific code is licensed under the same
license terms. PCRE and GD are external libraries which live outside
PHP's context and which are simply bundled. That's why the clear
preference there is PHP License.
OK, let
Hi George,
On Thu, Mar 27, 2008 at 8:11 PM, George Wang [EMAIL PROTECTED] wrote:
Hi Johannes,
Thank you for the quick reply.
Well, the idea is that all PHP-specific code is licensed under the same
license terms. PCRE and GD are external libraries which live outside
PHP's context
OK, let's back to the topic, is there any conclusion on this topic yet?
I certainly would like not to miss the release of 5.3 and ready to help
with any issue.
As to user request, here is one :-)
http://bugs.php.net/bug.php?id=42987
According to this ticket, this has been assigned to
Hi!
According to this ticket, this has been assigned to johannes, should I
follow up with this ticket to get it going?
Johannes is the RM for 5.3, so he decides if/when it gets in. :)
Our LSAPI library code has been license under BSD license, and there are
If extension and library are
Hi,
On Wed, 2008-03-26 at 16:07 -0400, George Wang wrote:
OK, let's back to the topic, is there any conclusion on this topic yet?
I certainly would like not to miss the release of 5.3 and ready to help
with any issue.
I think it makes sense, you, as the server's vendor, supports it and
Hi Andi,
On Tue, Mar 25, 2008 at 6:31 AM, Andi Gutmans [EMAIL PROTECTED] wrote:
Litespeed != lighttpd
I know, I only said that I'm a lighttpd user/shameless lightty ad :)
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
Btw, is this a multi-threaded SAPI or is it a FastCGI replacement? (i.e.
multi-process). Just curious...
Like FastCGI PHP, PHP with LiteSpeed SAPI run out of server process in
multi-process mode, the main difference to FastCGI SAPI is:
Highly optimized protocol to avoid overhead.
Built-in
Hi George
On Tue, Mar 25, 2008 at 3:05 PM, [EMAIL PROTECTED] wrote:
Highly optimized protocol to avoid overhead.
Built-in process manager to dynamically start/stop children processes
base on current load.
PHP configuration overridden via .htaccess
As of php 5.3, it is possible to have
Pierre,
As of php 5.3, it is possible to have a per directory configuration,
either using the system php.ini or using a .htaccess-like php.ini
(.user.ini). The concept is based on what you have in htscanner but in
a much better way (same syntax than in any php.ini). The goal is to
enable this
On Tue, Mar 25, 2008 at 6:11 PM, George Wang [EMAIL PROTECTED] wrote:
Pierre,
As of php 5.3, it is possible to have a per directory configuration,
either using the system php.ini or using a .htaccess-like php.ini
(.user.ini). The concept is based on what you have in htscanner but in
As of php 5.3, it is possible to have a per directory configuration,
either using the system php.ini or using a .htaccess-like php.ini
(.user.ini). The concept is based on what you have in htscanner but
in
a much better way (same syntax than in any php.ini). The goal is to
On Tue, Mar 25, 2008 at 8:43 PM, Uwe Schindler [EMAIL PROTECTED] wrote:
As of php 5.3, it is possible to have a per directory configuration,
either using the system php.ini or using a .htaccess-like php.ini
(.user.ini). The concept is based on what you have in htscanner but
in
Uwe Schindler kirjoitti:
As of php 5.3, it is possible to have a per directory configuration,
either using the system php.ini or using a .htaccess-like php.ini
(.user.ini). The concept is based on what you have in htscanner but
in
a much better way (same syntax than in any php.ini).
Is there a generic solution for SAPIs?
The stuff is pretty generic, just check how it's done for
sapi/cgi/cgi_main.c in
function sapi_cgi_activate(). (IIRC :)
I think I even put some comments in there..
Yes, looks good. Even the host-based config could be enabled by NSAPI.
The code
but it may also be possible to do all this in the request startup I think...?
I don't like the idea to keep adding stuff in request startup, at least,
please make it optional. The overhead for request startup and cleanup
have becoming higher and higher, which make PHP become slower and
On Tue, Mar 25, 2008 at 9:55 PM, George Wang [EMAIL PROTECTED] wrote:
but it may also be possible to do all this in the request startup I
think...?
I don't like the idea to keep adding stuff in request startup, at least,
please make it optional.
It is optional, it can be disabled
but it may also be possible to do all this in the request startup I
think...?
I don't like the idea to keep adding stuff in request startup, at least,
please make it optional. The overhead for request startup and cleanup
have becoming higher and higher, which make PHP become slower and
Hi,
It has been over two years since the last time we wrote to the list to
consider the inclusion of litespeed SAPI module in the stand PHP
distribution. By that time, our code has been added to CVS repository
under /pecl/litespeed, and I have been told that if there is enough
independent
Hi!
I believe, besides the apache SAPI and fcgi SAPI, LiteSpeed SAPI is one
of the top PHP SAPI being used in production environment. And LiteSpeed
SAPI has the combination of best performance, configuration flexibility
via .htaccess and enhanced security with SuEXEC.
I did not look into
Stanislav Malyshev wrote:
Hi!
I believe, besides the apache SAPI and fcgi SAPI, LiteSpeed SAPI is
one of the top PHP SAPI being used in production environment. And
LiteSpeed SAPI has the combination of best performance, configuration
flexibility via .htaccess and enhanced security with
You are right though, that we have other really odd SAPIs in the core,
but that is mostly a result of never having figured out how build a sapi
module standalone. Most of these really do belong in pecl if we could
solve the standalone issue.
Right, but if we didn't solve it - why we have
Well, popularity-wise it has about 0.003% of the web server market.
So I wouldn't put too much stock in that. We also have yet to ever
see a user request for it.
As to user request, here is one :-)
http://bugs.php.net/bug.php?id=42987
One of the reasons why did not receive much requests
Hi George,
On Mon, Mar 24, 2008 at 9:27 PM, George Wang [EMAIL PROTECTED] wrote:
It has been over two years since the last time we wrote to the list to
consider the inclusion of litespeed SAPI module in the stand PHP
distribution. By that time, our code has been added to CVS repository
To: George Wang
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Inclusion of PHP LiteSpeed SAPI in the standard
PHP distribution?
Hi George,
On Mon, Mar 24, 2008 at 9:27 PM, George Wang [EMAIL PROTECTED]
wrote:
It has been over two years since the last time we wrote to the list
28 matches
Mail list logo
