Stas, does this problem still persist for you?
On 19 August 2013 22:05, Michael Wallner m...@php.net wrote:
On 19 August 2013 00:01, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
Listening on http://localhost:8964
Document root is /home/smalyshev/php-src/sapi/cli/tests
Press Ctrl-C to
On Sat, Aug 3, 2013 at 8:16 PM, Nikita Popov nikita@gmail.com wrote:
Hi internals!
Is there any particular reason why we only pass return_value_ptr to
internal functions if they have the ACC_RETURN_REFERENCE flag set?
Why can't we always provide the retval ptr, even for functions that
Hi,
I prepared a patch to replace sapi_globals' request_info post_data and
raw_post_data with a temp stream and remove support for
HTTP_RAW_POST_DATA. [1]
PROS:
* save up to 300% on post_data_len memory (on non-form POSTs)
* a local siege (c=512/512, 2.4k form/2.2k json) showed no (negative)
On Tue, Aug 27, 2013 at 11:40 AM, Nikita Popov nikita@gmail.com wrote:
On Sat, Aug 3, 2013 at 8:16 PM, Nikita Popov nikita@gmail.com wrote:
Hi internals!
Is there any particular reason why we only pass return_value_ptr to
internal functions if they have the ACC_RETURN_REFERENCE
Dear list,
I recently ran into big problems with crc32() and ip2long() both of which I
was using in the same codebase.
I know these issues have been debated at length in the past, but this
really needs to be fixed.
Anytime you persist these values (to any external medium, files or
databases)
Hi,
I'm please to say that we keep processing the requests faster and faster,
leaving only few not handled in their first week. Thanks for everyone who
helped.
New:
#420 https://github.com/php/php-src/pull/420 Always provide retval ptr
#421 https://github.com/php/php-src/pull/421 Dedicated
On 27-08-2013 14:08, Michael Wallner wrote:
Hi,
I prepared a patch to replace sapi_globals' request_info post_data and
raw_post_data with a temp stream and remove support for
HTTP_RAW_POST_DATA. [1]
PROS:
* save up to 300% on post_data_len memory (on non-form POSTs)
* a local siege (c=512/512,
