Re: By way of example.

I beg to disapprove. You are making a mistake because you expect several 
protocols to play through the same interface (GET, PUT, POST, etc.) with 
a single URI.

As long as you will do that you will have a collision but that's your 
responsability and entirely out of APP's scope.

- Sylvain

Eric J. Bowman a écrit :
> I am using VARY, which is why my Content-Location returns:
>
> http://example.com/userid.atomsrv
>
> Which is because I chose to call my introspection document index.atomsrv.
>
> Which is all entirely irrelevant -- don't you see that whether or not I 
> locate the service document at http://example.com/index.atomsrv -or- if I 
> locate it at http://example.com/introspection...
>
> It is still a URI collision for ANYONE who implements it.
>
> Again, what are YOU GUYS returning in your Content-Location which does not 
> constitute the same exact URI collision I see in my implementation?
>
> THIS IS A FLAW WITH YOUR SPEC, NOT WITH MY SKILLS.
>
> -EJB
>
>   
> > -----Original Message-----
> > From: Thomas Broyer [mailto:t.broyer-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx]
> > Sent: Friday, August 18, 2006 11:52 AM
> > To: 'Atom-Protocol'
> > Subject: Re: By way of example.
> >
> >
> > 2006/8/18, Eric J. Bowman:
> >     
> > > > > No, it assumes that some mechanism may be in place that differentiates
> > > > > the requester; authentication credentials, for instance.  In our
> > > > > implementation, /introspection returns different data based on the
> > > > > authenticated identity of the requester.  No querystring parameters are
> > > > > required.
> > > > >
> > > > >           
> > > I will ask again.  Just how exactly have you implemented this?  By returning
> > > multiple resources at the same URI?  I asked what you were returning in
> > > Content-Location to differentiate /introspection between the individual users
> > > retrieving individual resources, without parameterizing the URL.
> > >
> > > I would still like an answer, instead of being told that only my
> > > implementation is incorrect by those who won't explain how theirs could
> > > possibly be made to work any differently than mine given that we've followed
> > > the same spec.
> > >       
> > GET /introspection HTTP/1.1
> > Host: example.net
> > ...
> >
> > HTTP/1.1 401 Unauthorized
> > WWW-Authenticate: Basic realm="..."
> > ...
> >
> > GET /introspection HTTP/1.1
> > Host: example.net
> > Authorization: ...
> > ...
> >
> > HTTP/1.1 200 OK
> > Vary: Authorization
> > ...
> >
> > Note that you could also use "Vary: *".
> >
> > --
> > Thomas Broyer
> >
> >
> >     
>
>