RE: [xacml] REST API -- finding a policy based on it's PolicyId

[<remon.sinnema@emc.com>]

Danny,


> -----Original Message-----
> From: xacml@lists.oasis-open.org [mailto:xacml@lists.oasis-open.org] On
> Behalf Of Danny Thorpe
> Sent: Friday, June 01, 2012 5:53 PM
> To: Sinnema, Remon; cforster@us.ibm.com
> Cc: xacml@lists.oasis-open.org
> Subject: RE: [xacml] REST API -- finding a policy based on it's
> PolicyId
> 
> Without a standardized way to address a specific policy revision in one
> network request knowing only the policy ID and version (or version
> range) desired, REST is not a good use case for PDP -> repository
> access.  The REST enumeration mechanism is fine for discovery when you
> aren't sure what you're looking for but not for direct addressing when
> you know exactly what you're looking for (policy ID & version).

Don't forget that a lot of the scalability in a RESTful system comes from caching. You don't have to start at the entry point for every single thing you want to do, because you'll have some resource further along the desired path already cached.


Thanks,
Ray