I think that's a great question, and I look forward to hearing others'
answers. I suspect that the correct "RESTful" answer would be that the URI
*is* the identifier.
On Wed, Mar 16, 2011 at 10:47 AM, Gili <cowwoc_at_bbs.darktech.org> wrote:
> If a user invokes HTTP PUT with a body that contains URIs, how should I
> translate those URIs back to resource identifiers? Am I expected to hit the
> URI, examine the body in order to figure out the resource identity or
> should
> I parse the URI to an ID somehow? What's the best practice?
>
> Thanks,
> Gili
>
> --
> View this message in context:
> http://jersey.576304.n2.nabble.com/Decoding-URI-into-path-parameters-tp6167750p6177050.html
> Sent from the Jersey mailing list archive at Nabble.com.
>