19 aug 2010 kl. 21.53 skrev Oleg Kalnichevski:
I am not sure I understand the intent of this library. Storage of
versioned response content for the same URI? Standards compliant HTTP
cache?
My use case is that I send a lot of requests, often the same request
to the same place. But most of the time I'm OK with a response of a
certain age. It is then way faster to just pick up an old response
from local persistency than to send a new request to the remote site
over the internet. And sometimes there are more reasons.
Once concrete example would be that I send a lot of requests to the
Google Geocoder API using HC. Not only will the response probably not
change within the next month, Google also have a daily query limit.
I could of course have implemented one cache for that specific use
case, but since I have quite a few other use cases this makes my life
simpler. Since I already use HC for everything it's nice not to have
to do anything but to replace HttpClient with my Wayback class.
karl
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
