On Aug 18, 2006, at 4:41 PM, Eric J. Bowman wrote:
http://example.com/service
This is a URI collision even if the only thing it serves up
is .atomsrv, even
if I expect only one protocol (APP) to dereference this.
Huh?
You keep saying this, and people keep saying "Huh?"
If the returned Content-Location looks like /service for all users,
this is
clearly a URI collision.
Huh?
I actually don't understand what the phrase "URI collision" means in
general, and I don't understand the specific meaning you're attaching
to it. Do you mean a situation where different people would get
different results from dereferencing this URI? That happens all the
time. A situation where people would get *incompatible* results?
That would be a problem. Is this problem inherent in APP? -Tim
