OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


Ray et al.

I too have been reading more of ODATA material, which, IMO, is a very solid and elegant protocol for general purpose exchange of data and metadata. As you are well aware of, there are a lots of similarities between the REST profile for XACML and ODATA; maybe is this just a matter of "specialization" whereas the REST profile for XACML could be considered as an instance of ODATA centered around the exchange of XACML policies/requests/responses. But there are surely differences that would then be worth documenting. I would even assume that the TC has already done and discuss those differences. Would you please provide the outcome of this analysis?

Thanks,
Jean-Paul Buu-Sao

-----Original Message-----
From: xacml@lists.oasis-open.org [mailto:xacml@lists.oasis-open.org] On Behalf Of remon.sinnema@emc.com
Sent: Saturday, June 02, 2012 00:01
To: Danny.Thorpe@quest.com
Cc: xacml@lists.oasis-open.org
Subject: RE: [xacml] REST API -- finding a policy based on it's PolicyId

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


---------------------------------------------------------------------
To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: xacml-help@lists.oasis-open.org



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]