Re: new ini parser, caching
| From: | Pierre | Date: | Wed, 12 Sep 2007 07:49:52 +0000 |
| Subject: | Re: new ini parser, caching | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-32280@lists.php.net to get a copy of this message | ||
On 9/12/07, Alexey Zakhlestin <indeyets@gmail.com> wrote:
> kqueue and "friends" allow you to skip that TTL part alltogether, as
> PHP can just register itself as a subscriber to filesystem events in
> related directories. If it notices that the file appeared or
> disappeared or changed it can react immediately, while still not
> making any "active" checks
(Warning: I never used these systems so I may be mistaken)
Unless they have a local session manager that allows php to register
once, get a SID and re connect on each request to fetch/catch the
notifications, it can't be used. It may be possible to store the
connection data and information in a persistent storage but the
problem of the notifcations remain, how will they be sent to PHP?
The advantage of a TTL system is its extreme simplicity and
portability (cache works per process child and work on every platform
supported by PHP).
Cheers,
--Pierre