Re: JSR311: Limit extensions pre-processing

From: Marc Hadley <Marc.Hadley_at_Sun.COM>
Date: Wed, 09 Jul 2008 14:31:33 +0200

On Jul 9, 2008, at 2:09 PM, Stephan Koops wrote:

> Hi Marc,
>> On Jul 9, 2008, at 12:46 PM, Dhanji R. Prasanna wrote:
>>> On Wed, Jul 9, 2008 at 6:52 PM, Marc Hadley <>
>>> wrote:
>>> URI opacity is an external thing, URIs aren't supposed to be
>>> opaque to the server - much of this JSR is concerned with URI
>>> cracking on the server side. I don't understand what you mean by
>>> "disrupting URI opacity" in this instance.
>>> All I mean is that a client is now required to know that deleting /
>>> blah.html will also remove /blah.xml.
>> Jerome was arguing the opposite, that you could delete blah.html
>> but leave blah and blah.xml unchanged.
> Dhanji means, what happens now in JAX-RS. Jerome means, what the
> request means.
I'm curious, wouldn't it also break URI opacity if you could:

GET /foo.html

but only


I.e. the client would have to know that the .html isn't part of the
resource identifier ?


Marc Hadley <marc.hadley at>
CTO Office, Sun Microsystems.