API Status

0 views
Skip to first unread message

Marc

unread,
Jan 29, 2009, 1:22:05 PM1/29/09
to CloudCache.ws
ReSTful API ready for testing and integration into plugins.

HTTP GET/PUT/POST/DELETE supported, appropriate http response codes
should be implemented but need testing and validation.

Auth is working on ReSTful API as well as "listkeys" - note that for
now, secret-key is "secret" - will be working on that soon as part of
the self-service signup and account page.

Once I have validation on auth for listkeys, I'll do the same for
list / myusage / flush.

Thinking I'll write a /stats method to show cache hits and misses.

Hoping to launch within weeks. It doesn't make sense to confuse new
users with old API version(s), so the ReSTful, aws-style auth version
of the API needs to be supported in all cases and the other deprecated
before launch.

We should also discuss here the RoR gem for CloudCache. Would be
great if were as simple as "$ gem install cloudcache" , prompted for
access key, secret key, done. Would be great if it were completely
API compatible with existing Cache interface.

Marc

unread,
Feb 3, 2009, 9:32:31 PM2/3/09
to CloudCache.ws
I've now added auth for list, myusage, and flush - with two ways to
enjoy ;^): akey, signature, and timestamp in either the headers or
in query parameters.

I uploaded test code, flush.py, list.py, myusage.py - those use the
header approach. Here's a url that uses the query param approach:
http://cloudcache.ws/myusage?akey=ccjava&signature=k%2BeHGDs1I8bLSqWCqGUvSeByFaY%3D&timestamp=y

(As you may note, it's not yet comparing timestamps...)

Cheers,


m
Reply all
Reply to author
Forward
0 new messages