Re: Re: HTTP::Cache vs HTTP::Download and HTTP::Header
| From: | Michael Wallner | Date: | Thu, 16 Dec 2004 16:44:31 +0000 |
| Subject: | Re: Re: HTTP::Cache vs HTTP::Download and HTTP::Header | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-35108@lists.php.net to get a copy of this message | ||
Hi Anatoly Techtonik, you wrote:
> Hello Michael,
> MW> If one's not able to find and use information and transform
> MW> it into knowlegde, well, one can be called quite lost nowadays...
> MW> If you've got any suggestions to improve the situation, provide
> MW> them in a sensible way, we'll very much appreciate them.
>
> Well, I suggest to merge the functionality of them into one package,
> which could be called HTTP::Cache_Control.
HTTP_Download supports much more than caching.
>>>I can only presume,
>>>that HTTP::Download implements something like PEAR wget
>
> MW> HTTP_Download is no downloader. The name might *now* be confusing,
> MW> but when the project started it was a real tiny "send some data" class.
> MW> See the package description, cvs and the docs for more information.
>
> The name *is* confusing and I'm not interested in some package history
> as long as I can't do that I need.
Pardon?
> HTTP::Download - Quote from manual:
[...]
>
> Where is something about Cache-Control here?
http://pear.php.net/manual/en/package.http.http-download.setcache.php
> What is "hidden downloads" BTW?
See example 33-2.
> I think it is downloader and descriptions confirm my thoughts.
http://pear.php.net/package/HTTP_Download
> I can't imagine how can I use downloader to control cache on the users
> side?
> If Downloader has such Cache functionality I propose to detach this
> functionality into separate logical concept and establish a
> dependancy. That will be logicaly correct. If you want an argue -
> place a voting:
>
> "How should be called package implementing HTTP cache control
> mechanisms described in chapter > 13.1.3 of HTTP RFC
> http://www.faqs.org/rfcs/rfc2616.html ?"
I won't repeat - I already said why its name is HTTP_Download,
please read the archives for more information. A naming debate is
for me as well out of place as detaching this functionality.
> MW> Well, then have another look. Many people are already using these
> MW> classes successfully. If you foind a bug while using them, please
> MW> report (if not needless to say).
>
> Many? Let's assume there is package download statistics and most of
> them using these packages to "handle (hidden) downloads. It supports
> partial downloads, resuming and sending raw data ie. from database BLOBs."
> How many of them use Cache-Control techniques from these packages?
> How many use different Cache-Control packages and why don't they use
> HTTP::Download and HTTP::Header for that purpose?
Don't ask me - make a survey.
> What is Ueber, BTW? =)
http://en.wikipedia.org/wiki/Ueber
Regards,
--
Michael - < mike(@)php.net >
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc