Re: Google Docs as capabilities as data
Domenico Rotondi <[email protected]>
| Newsgroups | gmane.comp.capabilities.general |
|---|---|
| Message-ID | <[email protected]> |
On 29 Jan 2014 at 11:13, Raoul Duke wrote:
Thanks. See comments in line.
Ciao
Domenico
> > within the EU FP7 IoT@Work project (http://www.iot-at-work.eu/) we used
> > capabilities to manage access to a publish/subscribe service tailored for
> > shop floor events collection and dispatching.
> > [...details...]
>
> holy cow, that was pretty amazing to hear. nice that there are people
> actually really using caps.
>
> i thought the distributed nature was very cool.
>
> ...up until:
>
> > call revocation requests that are submitted to a specific revocation service
>
> oh well. can't have it all, i guess. ;-) unless i'm missing something,
> it sounds like the revocation service is sort of a single point of
> failure?
Actually you can have many revocation services that serve distinct service or
resource providers. BTW the revocation service is deintified via a URL and exposes
a REST API so it can actually be a cluster.
The only real constraints are:
* the revocation service URL must be reported in the capability tokens for the
service/resource associated to that revocation service (but it could act as
revocation service for many services/resources)
* the service has to know which revocation service it has to contact (in reality there
is a Policy Decision Point in between; so the service or resource manager does its
checks with the PDP)
>
> sincerely.
_______________________________________________
cap-talk mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/cap-talk