RESTful Storage API ?

Tom Zeller tzeller at dragonacea.biz
Tue Jun 11 15:03:23 EDT 2013


> I don't know, it's six of one to do something like that internally in a storage plugin itself, in which case you don't have to standardize that interface. What's the use case in general? It's pretty much memcache to stick an API in front of an in-memory store on some other shared host.

Nothing fancy, the general use case I was thinking of is N IdPs
configured to use the same StorageService for redundancy and
load-balancing of the IdPs. I was reading the Storage API and thought,
well, non-primitive method parameters would preclude a RESTful
interface.

If memcahe is the answer, fine, I was not sure what our dependency there was.

I thought that a REST API for ToU and Consent might be helpful if that
data might be supplied out-of-band, meaning not via an IdP flow.

> There are very few true REST APIs that I've ever seen and I don't spend much time thinking about it, so I wouldn't really know what to do make an API not require an abstraction layer, or why that would even be a problem.

Not a problem, just a comment.


More information about the dev mailing list