Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:59436 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60533 invoked from network); 7 Apr 2012 18:22:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Apr 2012 18:22:22 -0000 Authentication-Results: pb1.pair.com header.from=luke@cywh.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=luke@cywh.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain cywh.com from 209.85.212.42 cause and error) X-PHP-List-Original-Sender: luke@cywh.com X-Host-Fingerprint: 209.85.212.42 mail-vb0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:39237] helo=mail-vb0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FD/4E-23111-DD5808F4 for ; Sat, 07 Apr 2012 14:22:22 -0400 Received: by vbjk13 with SMTP id k13so1970446vbj.29 for ; Sat, 07 Apr 2012 11:22:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=6B1oLmALlyNqDzQ2K2WEtCfHiitFcuu2QWtpRQW5w4M=; b=A0WMmuR1n93TqKkRgbBC2b6Uw2gI5vDzBwR+vsBstitM+DTNR88NjClyIYvHTET5X/ KtmroetdFixdqk3ae+Lcnwbdq02VaONM/hGsueo18uY464C8kg9BjoEHg+9k/VmxWxpL g6l5yHfHBWTSV44IGvgXaZddj2Fyi+wx8UN3/L5UOV8dT3HTGaoSj6qD8xp4kxOT/kXE OANAACH8Xvas2DME10Nd3HgwnSzdW/88QXAXSP7t2mgtEe0P+aqxzwQ5KCF3FyQIVNy8 l6VyxuKanE4xnGIhaLN/fwHmL0klaK9JFQAaModW5ccLYOQwluvshUSFQoNNvHB674sm T4wA== Received: by 10.220.180.132 with SMTP id bu4mr998625vcb.11.1333822938221; Sat, 07 Apr 2012 11:22:18 -0700 (PDT) References: <11343239.3338.1333757773882.JavaMail.mobile-sync@iakr3> <1722329293808329363@unknownmsgid> <4F7FD377.9030207@sugarcrm.com> <-8675298664786638901@unknownmsgid> In-Reply-To: Mime-Version: 1.0 (1.0) Date: Sat, 7 Apr 2012 11:22:16 -0700 Message-ID: <6299038408217970525@unknownmsgid> To: Pierre Joye Cc: Stas Malyshev , PHP Internals Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQl+hKAqPAii5zz/ss/erig0Ln+hndP1xvN2lvr85vItk2LHw4Ae92V8g/mGF4QPvHMK1GgJ Subject: Re: [PHP-DEV] Persistent zvals From: luke@cywh.com (Luke Scott) On Apr 7, 2012, at 11:14 AM, Pierre Joye wrote: > On Sat, Apr 7, 2012 at 6:51 PM, Luke Scott 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 :). An application server would be cool though. I was thinking along the lines of having each process be an instance of the application.. thus the idea about persisting objects. >> 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. How would that work? I'm intrigued. Luke > > Cheers, > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org