Re: Re: Packages'name and extensions of PEAR

Hi,

Slowly I wonder what's wrong with HTTP_Download? :) If caching by ETag does not work with HTTP_Download for you, I'd really appreciate a bug report... There's nothing wrong with HTTP_Download, I'm using this in my applications (though not with cached data), but still you have to choose whether to include HTTP_Download or HTTP_Header_Cache, based on the type of cache you want.

That's the only thing that bugs me... But I'll probably just delete the proposal, as the functionality already is in PEAR and this seems to be sufficient for the majority. If I should find the time and a solution how to integrate this smoothtly in HTTP_Header_Cache, I'll let you know.

Obviously some don't like to have another HTTP_Cache package in PAER, so I could make you a lead of HTTP_Header and you put your ETag caching class into this package and can release HTTP_Header yourself... No need for that. Thanks anyway.

Best regards,