Re: Modeling permissions with Hydra

On Tue, Nov 10, 2015 at 4:42 PM, Markus Lanthaler
<markus.lanthaler@gmx.net> wrote:
> The reason this was designed this way is that in most APIs out there, typically (almost) all instances of a specific type typically support exactly the same operations. You don't see a lot of APIs where each resource behaves completely differently from every other resource exposed by the API.

I disagree; one sees exactly this in APIs where the supported
operations are determined by a role-based permissions system,
especially if the roles themselves are dynamic (one can define and
assign new roles). Besides, one of the reasons one may not see so many
APIs like this currently is that there hasn't been a great way to
write real hypermedia clients that can handle such dynamic APIs, but
isn't that what you are enabling with Hydra?

Ryan

Received on Wednesday, 11 November 2015 21:39:09 UTC