On 8/18/06, Eric J. Bowman <eric-MkmoNbc1SAncr/OS1auqaA@xxxxxxxxxxxxxxxx> wrote:
>
>Ok, first, it would seriously help the conversation if you just simply
>stopped using the term "URI collision".
>
It was my work which was so characterized. Since the problem I describe fits
the definition of that term, I see no reason to change until someone
convinces me that Mary's collection is the same resource as Joe's collection
and that each user receives a _version_ of some master document listing
everybody's collection (i.e. index.atomsrv).
>
>Second, what's the problem? So different users get different results
>when calling the same URI. Happens all the time. If you navigate to the
>URI http://www.google.com/ig?hl=en, you'll see a different result than
>what I see. No big deal.
>
No, I'm sorry, that does not happen all the time. When I dereference:
http://example.com/index.atomsrv
I should see a representation of index.atomsrv, not some other resource
user.atomsrv which is NOT derived from the resource I dereferenced. If I
then dereference that URI from a different workstation and it returns
user2.atomsrv, this is also not a representation of index.atomsrv but is also
an entirely separate resource which bears no resemblance to user.atomsrv,
despite sharing the same URI.
If I dereference these:
http://www.example.com/instructions?hl=en
http://www.example.com/instructions?hl=es
and the first URI returns English-language instructions for lawnmower repair
but the second URI returns Spanish-language instructions for making a martini
we have a problem, typically referred to as a URI collision. If they are
both returning instructions for the same thing we have a perfectly good use
of content negotiation to choose the correct language representation of the
same resource.
OK, I'm now a member of the "Land of the Lost" too. Is the difference
in content based upon authentication? Access workastion? Whether I
mow lawns or am a bartender?
Your example is completely incomprehensible.
-- Kyle
