Re: Persistent zvals

On Sat, Apr 7, 2012 at 6:51 PM, Luke Scott <luke@cywh.com> wrote: > I think I understand what you're getting at. So to avoid fragmentation > you would have to have two independent memory spaces. Making non > persistent memory persistent would require copying from one space to > another. Is that correct? Yes, that's correct. > How is this handled in other platforms where you have an application > instance (with state, if that's the correct terminology)? Application server is something different. PHP is not one, as it could be possible to do that using the builtin web server (dev only :). > Are there any other options for reliably persisting objects/variables > (without having to recreate)? Something I have been discussed in the past with a couple of persons is to have a mechanism to automatically instantiate objects on request start. That's not persistent objects but that could already boost a little it the base foot print of some frameworks. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org