Re: HTTP::Cache vs HTTP::Download and HTTP::Header
| From: | Michael Wallner | Date: | Thu, 09 Dec 2004 19:38:33 +0000 |
| Subject: | Re: HTTP::Cache vs HTTP::Download and HTTP::Header | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-34978@lists.php.net to get a copy of this message | ||
Hi Anatoly Techtonik, you wrote:
> 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.
If one's not able to find and use information and transform
it into knowlegde, well, one can be called quite lost nowadays...
If you've got any suggestions to improve the situation, provide
them in a sensible way, we'll very much appreciate them.
> I can only presume,
> that HTTP::Download implements something like PEAR wget
HTTP_Download is no downloader. The name might *now* be confusing,
but when the project started it was a real tiny "send some data" class.
See the package description, cvs and the docs for more information.
> 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.
Well, then have another look. Many people are already using these
classes successfully. If you foind a bug while using them, please
report (if not needless to say).
> 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.
See point (1).
> 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. =)
I doubt that anybody will be against some UeberCache package... :)
As long as that package doesn't exist, my answer is quite simple:
You can use HTTP_Header_Cache for unpersonalized and HTTP_Download
for personalized pages, which should be cached on the client side.
Regards,
--
Michael - < mike(@)php.net >
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc