Hi!
> Connection pooling could be a good usage of this if we manage to get
> this working again.
Connection pooling is persisting external resources, usually, which can
be done with little regard to zvals, since zval for resource is just a
container holding an opaque pointer. A number of extensio
IIRC, we used to support that back in ~2000s, but it got removed based on
the lack of usage and poor implementation.
Connection pooling could be a good usage of this if we manage to get this
working again.
[]s,
On Thu, Dec 11, 2014 at 1:46 PM, Marc Bennewitz wrote:
>
> Am 10.12.2014 um 09:53 s
Am 10.12.2014 um 09:53 schrieb Stanislav Malyshev:
Hi!
Why?
There is a reference counter, which should be increased on put a value
into persistence and on removing a value from persistence decrease it.
So the GC could handle unreferenced zvals.
Because memory which is allocated by the engine
Hi!
> Why?
>
> There is a reference counter, which should be increased on put a value
> into persistence and on removing a value from persistence decrease it.
> So the GC could handle unreferenced zvals.
Because memory which is allocated by the engine is freed at the end of
the request. You coul
> On 9 Dec 2014, at 19:45, Marc Bennewitz wrote:
>
>
> Am 09.12.2014 um 20:03 schrieb Sara Golemon:
>> On Tue, Dec 9, 2014 at 10:58 AM, Marc Bennewitz wrote:
>>> Is it possible to make a zval persistent?
>>>
>> Nope.
>>
> Why?
>
> There is a reference counter, which should be increased on p
Am 09.12.2014 um 20:03 schrieb Sara Golemon:
On Tue, Dec 9, 2014 at 10:58 AM, Marc Bennewitz wrote:
Is it possible to make a zval persistent?
Nope.
Why?
There is a reference counter, which should be increased on put a value
into persistence and on removing a value from persistence decrea
On Tue, Dec 9, 2014 at 10:58 AM, Marc Bennewitz wrote:
> Is it possible to make a zval persistent?
>
Nope.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
