HTTP::Cache vs HTTP::Download and HTTP::Header
| From: | anatoly techtonik | Date: | Thu, 09 Dec 2004 18:28:20 +0000 |
| Subject: | HTTP::Cache vs HTTP::Download and HTTP::Header | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-34974@lists.php.net to get a copy of this message | ||
Hello pear-dev,
HTTP::Cache vs HTTP::Download and HTTP::Header
If there is such thing as usability in PEAR, then I must admit, that
above conflict directly relates to it. As an unexperienced developer
I know which packages PEAR contain but I just don't have time to read
each and all descriptions available on the site. I can only presume,
that HTTP::Download implements something like PEAR wget and
HTTP::Header is for some mysterious HTTP headers manipulations or for
statistics or whatever. It was a big surprise to know them capable
something else.
From my POV if I need to implement Cache Control for my site, I will
feed google these words "cache control php package". Useful package is
not that it contains many features, but one, which developers know
about and use.
I'd like to have some HTTP::Cache_Control, which specializes only on
this part of HTTP protocol, even if it will bear some of the other
packages functionality. But this one should implement the ultimate
Caching mechanizm if it is possible. =)
t
--