Re: persistent storage in PHP
| From: | Ed | Date: | Thu, 08 May 2003 03:15:39 +0000 |
| Subject: | Re: persistent storage in PHP | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-146779@lists.php.net to get a copy of this message | ||
Check the Shmop's http://www.php.net/manual/en/ref.shmop.php
Note that they do not seem to be "thread safe" as shmop_read does:
memcpy(return_string, startaddr, bytes);
shmop_write does:
memcpy(shmop->addr + offset, data, writesize);
I did not see any inter-process "mutexing" going on, but I could be wrong.
Ed
----- Original Message -----
From: "Justin French" <justin@indent.com.au>
To: "Greg Stark" <greg-spare-1@mit.edu>; <php-general@lists.php.net>
Sent: Wednesday, May 07, 2003 7:41 PM
Subject: Re: [PHP] persistent storage in PHP
> on 08/05/03 9:47 AM, Greg Stark (greg-spare-1@mit.edu) wrote:
>
> > Woah, I guess my question was ambiguous. I'm not talking about data
persisting
> > from one page access to the next for a given user. I'm talking about
data
> > persisting from one user to the next for a given web server process.
> >
> > I'm talking about data that will be inserted into the template for every
> > single page access, so I don't want to add an extra database call. And
data
> > that changes very infrequently, actually probably never once the site
goes
> > live.
>
> You can have a file that is auto-prepended to the beginning of every PHP
> request... look at it as an include() that you don't have to type at the
top
> of each script.
>
> I auto-prepend my config file to the start of all scripts.
>
> Not sure if this helps your particular needs.
>
>
> Justin
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>