Re: Re: [PEPr] Proposal for HTTP::HTTP_Cache
| From: | bertrand Gugger | Date: | Thu, 09 Dec 2004 13:57:06 +0000 |
| Subject: | Re: Re: [PEPr] Proposal for HTTP::HTTP_Cache | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-34957@lists.php.net to get a copy of this message | ||
Hi Stephan & Pierre-Alain,
I'm sorry to go on this allready very long discussion, but it started to quiz me ;)
I mean, an half way is certainly possible fot his ETag extension:
some kind of PEAR/Cache/ETag.php supplementary submodule
(Stephan: your code's basic class redefining the existing Cache class from PEAR)
I took a look in PEAR::Cache and it's allready a mixed of very different interfaces.
Nothing is unified there.
The public methods are absolutely different if you want to catch different stuff.
So the Etag.php could also be quite free to do what it wants.
Could share the container methods what is nowhere to be seen in your proposal.
à+
--
bertrand Gugger (toggg)