Re: By way of example.

Ok, well, at least now I think I understand what you're trying to say.
I still completely disagree with it, but hey, I guess it's progress
nonetheless....

- James

Eric J. Bowman wrote:
>> In one of my implementations, our service doc is always available
>> through the same uri..
>>
>>  http://example.org/oa/service/atom/introspection
>>
>> The content of the returned document varies depending on the
>> authentication credentials of the caller.
>>
> 
> My point exactly.  You have multiple resources, one for each user, sharing 
> the same address with no distinction between them, which is _exactly_ why it 
> is good practice to return a distinguishing Content-Location to the client.
>
> Each of those resources needs its own URI if you want to access them in a 
> RESTful fashion instead of an RPC fashion, whether you return that URI in a 
> Content-Location is indeed optional but the point is it's something you 
> should be able to do.  If you can't you have, by definition, a URI collision.
> 
> -EJB
>