> > But how would you specify where this code is? Sessions are
> > destroyed out
> > of context.
>
> ok, a __destroy method implies that the method is bound to the object, but i was
>thinking of a static method that gets the session information for the object and can
>obtain the instance with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> But how would you specify where this code is? Sessions are
> destroyed out
> of context.
ok, a __destroy method implies that the method is bound to the object, but i was
thinking of a static method that gets the session information for the ob
> > You mean, when the session is destroyed it should call
> > __destroy_callback?
>
> exactly.
But how would you specify where this code is? Sessions are destroyed out
of context. ie. a session is not necessarily destroyed by anything even
remotely resembling the script that created them.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> You mean, when the session is destroyed it should call
> __destroy_callback?
exactly.
> Anyways, don't those objects store a resource handle in their
> properties?
"The magic functions __sleep and __wakeup
serialize() checks if your class h
On Thu, 06 Dec 2001, Harald Radi wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> actually it isn't a resource but an object implementing __sleep and
> __wakeup. so technically there should be no problem. i'd only need a
> __destroy callback or sg. similar.
You mean, when the ses
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
actually it isn't a resource but an object implementing __sleep and __wakeup. so
technically there should be no problem. i'd only need a __destroy callback or sg.
similar.
harald
> -Original Message-
> From: Andrei Zmievski [mailto:[EMAI
On Thu, 06 Dec 2001, Harald Radi wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> hi,
>
> do you think of a possibility to add something like the
> zend_register_list_destructors() mechanism into your session extension
> to register session destructors for resources ? i'd like to
