RESTful Storage API ?

[Cantor, Scott]

> 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.

Not exactly. They just become artifacts of a URL.

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

I don't know if it's better or worse to do something else, I'm not in general into the idea of a single point of failure as a clustering solution because it means the whole thing is down if you have to patch the single point.

> 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.

Actually, more to the point they could work well with a best-effort store vs. something transactional in some cases.

But in terms of programming, no, I prefer having an API and letting it handle things like remoting, than the other way around.

-- Scott