Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:12203 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76603 invoked by uid 1010); 17 Aug 2004 23:46:09 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 76550 invoked from network); 17 Aug 2004 23:46:08 -0000 Received: from unknown (HELO xaxa.search.ch) (195.141.85.117) by pb1.pair.com with SMTP; 17 Aug 2004 23:46:08 -0000 Received: from localhost (localhost [127.0.0.1]) by xaxa.search.ch (Postfix) with ESMTP id 1821F6D82F; Wed, 18 Aug 2004 01:46:08 +0200 (CEST) Received: by xaxa.search.ch (Postfix, from userid 65534) id CC9506D857; Wed, 18 Aug 2004 01:46:06 +0200 (CEST) Received: from [192.168.0.42] (ultrafilter-i [192.168.85.2]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by xaxa.search.ch (Postfix) with ESMTP id 553266D82F; Wed, 18 Aug 2004 01:46:06 +0200 (CEST) Message-ID: <412298BD.10407@cschneid.com> Date: Wed, 18 Aug 2004 01:46:05 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040804 X-Accept-Language: en-us, en, de-ch, de MIME-Version: 1.0 To: Andi Gutmans Cc: internals@lists.php.net References: <5.1.0.14.2.20040817161212.044edd50@127.0.0.1> In-Reply-To: <5.1.0.14.2.20040817161212.044edd50@127.0.0.1> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on xaxa.search.ch X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.64 X-Virus-Scanned: by AMaViS 0.3.12pre8 Subject: Re: setcookie() and Max-Age From: cschneid@cschneid.com (Christian Schneider) Andi Gutmans wrote: > Not sure if an how this could be added to setcookie() because of the > already rich amount of parameters it accepts. Would it make sense to > have something like setcookie_max_age() or something similar? I think we should overload the expire parameter. Somewhat ugly but transforms the function into what it really should look like. Adding another parameter or even function complicates the life of everyone in the future and since a IMHO doable way exists I'd say we should keep it simple. Proposal: expire < 1000000000 (Sun Sep 9 01:46:40 2001) uses Max-Age and allows up to 31 years of Max-Age. If properly documented this should be ok IMHO. If people are afraid that someone hardcoded something before Sun Sep 9 2001 in their source code then we could lower it to 100000000 (Sat Mar 3 09:46:40 1973, 3.1 years) but I'd prefer the previous value. My .02$, - Chris