Thanks for your feed-back!
In version 2.0, we have added support for all caching headers in the
Restlet API. See this page for the mapping table:
http://wiki.restlet.org/docs_2.0/13-restlet/27-restlet/324-restlet/130-restlet.html
It is threrefore very easily to retrieve all cache related information
for a remote resource and to send conditional requests as well. Are you
looking for something different?
We are also planning further caching support for future releases, mainly
to plug with actual caching stores on the server or client side. See
this RFE for details:
http://restlet.tigris.org/issues/show_bug.cgi?id=25
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Technical Lead ~ http://www.restlet.org
Noelios Technologies ~ http://www.noelios.com
Le 24/04/2010 19:46, Streets Of Boston a écrit :
Hi Jerome,
I'm using your restlet libaries as well on Android clients. So far, it
has worked great :-)
One thing i'd love to see implemented is a framework that helps in
implementing caches. Not so much the implementation and handling of an
actual cache, but some framework part of Restlet that handles all the
Cache, E-Tag, If-modified, etc., headers. The only thing left for a
client to do, that would use this Restlet framework, is to register
callbacks (implementing an interface?) that can tell the Restlet about
the cache-information/status of a given resource and that can allow
the Restlet to request a resource to be saved to, read from or deleted
from the cache.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en