On Wed, Sep 09, 2009 at 03:42:44AM +0100, dreamcat four wrote:
> > Not sure about bundling libevent though - does it have to be bundled?
> Don't know. Libevent is frozen in there and a couple of files were
> modified with references back into the fpm headers.
> The Libevent was updated recently any
On Tue, Sep 8, 2009 at 8:58 PM, Stanislav Malyshev wrote:
> As for bundling libevent, I have no idea if BSD code can be put in php
> tree... It'd be much nicer if these chanegs were merged into libevent - it
> seems to be pretty alive, 3 releases this year.
That's what I've been saying. If it's s
Hi!
Its coming with it's own ./configure. I think you can hang one
I'd suspect most of what it's configure is doing is done by the php one
too, and the rest can be converted to PHP's configure fragment. The
thing is that if you want to have it in PHP tree, it won't look too good
for it to h
I found same problem in IIS recently.
When SSL connection established and read to eof,I can't write anything
to stream again.
It's trow :SSL operation failed with code 1. OpenSSL Error messages:
error:140D00CF:SSL routines:func(208):reason(207).
My php version is 5.2.9
2009/9/8 Eloy Bote Falcon :
On Wed, Sep 9, 2009 at 2:23 AM, Stanislav Malyshev wrote:
> Hi!
>
>> The question is: Do you want fpm-sapi (or not)?
>
> If it applies cleanly to PHP and doesn't require changes in the core, then
> why not?
> But for that I guess there should be some build modifications that make
> common build (i.
Hi!
The question is: Do you want fpm-sapi (or not)?
If it applies cleanly to PHP and doesn't require changes in the core,
then why not?
But for that I guess there should be some build modifications that make
common build (i.e., as for other modules - one runs configure/make and
gets the bin
I'm 99% sure, this proposal this time around is for a seperate SAPI
only. So that's not the question being asked here.
The question is: Do you want fpm-sapi (or not)?
On Wed, Sep 9, 2009 at 1:01 AM, Rasmus Lerdorf wrote:
> This has been discussed before. See:
> http://news.php.net/php.internals/4
This has been discussed before. See:
http://news.php.net/php.internals/44476
http://news.php.net/php.internals/44480
http://news.php.net/php.internals/44484
http://news.php.net/php.internals/44485
Basically it comes down to figuring out whether to extend the existing
FastCGI SAPI to support the p
Hi!
We have today been asked by Debian and Ubuntu Maintainers to merge our
code up to PHP repository.
They have stated that they want to see the fpm sapi variant officially
supported.
It would be nice to hear what you guy's official decision would be
about something like this.
Here are some detai
Hmmm.
stream_get_line doesn't appear to work correctly with bz streams:
--example.php--
$tmpname = tempnam("/tmp", "tmp");
$tmp = fopen($tmpname, "w");
stream_filter_append($tmp, 'bzip2.compress', STREAM_FILTER_WRITE);
fwrite($tmp, "line1\n");
fwrite($tmp, "line2\n");
fwrite($tmp, "line3");
fclos
Well, that's a really good question.
Pre-patch, at the end of the stream (when you don't explicitly seek), you get
empty strings:
--example.php--
$tmp = tmpfile();
fwrite($tmp, "line1\r\n");
fseek($tmp, 0);
var_dump(stream_get_line($tmp, null, "\r\n"));
var_dump(stream_get_line($tmp, null, "\r\
> Hi,
> Can this snippet of shebang checking be removed for php 5.3.+, 6?
> Its for external FPM project.
>
> cgi_main.c:
> php_fopen_primary_script(&file_handle TSRMLS_CC);
>
> if (CGIG(check_shebang_line) && file_handle.handle.fp &&
> (file_handle.handle.fp != stdin)) {
> /* #!php support */
> c
Hi,
Can this snippet of shebang checking be removed for php 5.3.+, 6?
Its for external FPM project.
cgi_main.c:
php_fopen_primary_script(&file_handle TSRMLS_CC);
if (CGIG(check_shebang_line) && file_handle.handle.fp &&
(file_handle.handle.fp != stdin)) {
13 matches
Mail list logo
