Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:32280 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37867 invoked by uid 1010); 12 Sep 2007 07:49:56 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 37852 invoked from network); 12 Sep 2007 07:49:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Sep 2007 07:49:56 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.186 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.198.186 rv-out-0910.google.com Received: from [209.85.198.186] ([209.85.198.186:38012] helo=rv-out-0910.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 53/FA-57702-32A97E64 for ; Wed, 12 Sep 2007 03:49:56 -0400 Received: by rv-out-0910.google.com with SMTP id k15so119626rvb for ; Wed, 12 Sep 2007 00:49:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=f7Kv/nYOqo2SMRCTLphoh/CQC6BPIg0c8cGtRBqwKsY=; b=tR7vRoVrX8tF11iE7YNwxaMy02JlHulI1/o7xLY++ze6gBCNrOSKKNTCneWVlU3ZDJg646KaFIzszi4PYTYbeJUjTRBP28j2dMQO6ojIDxooQzjq9jEZH+trx7Ldqjkcpy4yr7XElwyzWgUAProPyC8kjTT9/JTfimfT8zqLV5I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Rj2WnuvQCX/CxpwDd0YORxJ5kJfXJEzz5fKsZf88antL8rl31m4V5VAhgZhsm3csuSA4P4RgPUh/EpVsjFGE4bfTlAfLUD8lbW4YwcviPTfpVH/VFiCwbdivOZHcQsv8XndJw0NEQqG3AVWmS69COGvY+ZwsUJcZYFE0HRmUIuE= Received: by 10.141.164.10 with SMTP id r10mr80682rvo.1189583392943; Wed, 12 Sep 2007 00:49:52 -0700 (PDT) Received: by 10.141.37.7 with HTTP; Wed, 12 Sep 2007 00:49:52 -0700 (PDT) Message-ID: Date: Wed, 12 Sep 2007 09:49:52 +0200 To: "Alexey Zakhlestin" Cc: "Stanislav Malyshev" , jani.taskinen@iki.fi, "Andi Gutmans" , "Ilia Alshanetsky" , "PHP Developers Mailing List" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46E6C3A6.7070309@zend.com> Subject: Re: [PHP-DEV] new ini parser, caching From: pierre.php@gmail.com (Pierre) On 9/12/07, Alexey Zakhlestin 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