On 7/28/2010 10:16 AM, jsm wrote:
Gavin,
You are right about the overhead and also saw that API's exist for
most of the languages as well.
I thought REST API would make memcached language agnostic.
I would like to hear from the community if the REST API should be
pursued or not?

I'm not quite sure how a rest api could deal with the distributed servers without a special client anyway. But, it might be handy to have a web service that mapped a rest api as directly as possible to memcache operations where the http side would use traditional load balance/fail over methods and handle the http 1.1 connection caching. I'm sure there would be places where this could be used by components that have/want data in a cache shared by more efficient clients.

--
  Les Mikesell
   [email protected]

Reply via email to