Return-Path: Delivered-To: apmail-httpd-apreq-dev-archive@www.apache.org Received: (qmail 61724 invoked from network); 24 May 2005 20:16:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 May 2005 20:16:44 -0000 Received: (qmail 54032 invoked by uid 500); 24 May 2005 20:16:44 -0000 Delivered-To: apmail-httpd-apreq-dev-archive@httpd.apache.org Received: (qmail 54013 invoked by uid 500); 24 May 2005 20:16:43 -0000 Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list apreq-dev@httpd.apache.org Received: (qmail 53999 invoked by uid 99); 24 May 2005 20:16:43 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from Unknown (HELO goonhilly.openstrike.co.uk) (213.174.199.247) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 24 May 2005 13:16:42 -0700 Received: from sputnik.openstrike.co.uk (cpc2-sals1-5-0-cust152.sot3.cable.ntl.com [82.7.193.152]) (authenticated bits=128) by goonhilly.openstrike.co.uk (8.12.10/8.12.10) with ESMTP id j4OKGcjU006475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 24 May 2005 21:16:39 +0100 Received: from sputnik.openstrike.co.uk (sputnik [127.0.0.1]) by sputnik.openstrike.co.uk (8.13.1/8.13.1) with ESMTP id j4OKGZTF006221 for ; Tue, 24 May 2005 21:16:35 +0100 Received: (from pete@localhost) by sputnik.openstrike.co.uk (8.13.1/8.13.1/Submit) id j4OKGZBF006220 for apreq-dev@httpd.apache.org; Tue, 24 May 2005 21:16:35 +0100 Date: Tue, 24 May 2005 21:16:35 +0100 From: Pete Houston To: apreq-dev@httpd.apache.org Subject: Re: Apache2::Cookie::Jar->cookies($key) doesn't work anymore? Message-ID: <20050524201635.GF3707@sputnik.openstrike.co.uk> References: <200505241202.18863.nomis80@lqt.ca> <87wtpofsmh.fsf@gemini.sunstarsys.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1Y7d0dPL928TPQbc" Content-Disposition: inline In-Reply-To: <87wtpofsmh.fsf@gemini.sunstarsys.com> User-Agent: Mutt/1.4.1i Organization: Openstrike X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --1Y7d0dPL928TPQbc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable At the moment, I'm using this to get at the cookie contents: %cookies =3D Apache2::Cookie->fetch($r); $value =3D $cookies{'prefs'}->value; if ($value) { %cv =3D Apache2::Cookie->thaw($value); } where 'prefs' is the cookie name. This works in 2.05 fine, but I'm not convinced that it's=20 (a) the most efficient method (b) the most elegant method (c) the most forward-compatible method Although Simon's method probably wins on point (b), how do these approaches compare for (a) and (c), or is there a better way entirely? Pete On Tue, May 24, 2005 at 01:20:22PM -0400, Joe Schaefer wrote: > Simon Perreault writes: >=20 > > Re-hi, > > > > I've come to realize that I, as a user of libapreq, shouldn't be > > playing with APR::* classes, but with the Apache2::* classes instead. >=20 > No, you shouldn't do that, because the APR::* classes will be the > ones we recommend nowadays. We debated whether to chuck the Apache2::* > classes entirely, but we left them in for back-compat reasons. > It doesn't surprise me that we broke lots of stuff in the=20 > Apache2::* APIs with 2.05-dev, but we consider most of those=20 > breakages as bugs to fix. >=20 > > I'll try to ask my question in as general a way as possible so as not > > to get into things that are way over my head. > > > > Apache2::Cookie::Jar->cookies($key) doesn't seem to work anymore in 2.0= 5. >=20 > Nope, and that's another bug I suppose (although I > don't think cookies() was ever intended to be a class > method). >=20 >=20 > --=20 > Joe Schaefer --=20 Openstrike - improving business through open source http://www.openstrike.co.uk/ or call 07092 020107 --1Y7d0dPL928TPQbc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFCk4ujdzfnYmsKt50RAtwXAKCrRo2xjCZbjmLZa2BRAPI0yiarjACgiHTQ +ypjrifsSx7jxkhr0FfPGW0= =2BPx -----END PGP SIGNATURE----- --1Y7d0dPL928TPQbc--