On 15/12/2010 14:48, Gary Lawrence Murphy wrote:
> thanks.  I just might :)  I can probably find it on Google, but would you
> happen to have the url for the jsr-315 spec?

You can grab it from http://jcp.org/en/jsr/detail?id=315

Mark

> I still find it incredible
> that a 15 year mature unix-originating project in 2010 would still be
> demanding CPM/MSDOS filename extensions and not simply using the standard
> regex library, or that java servers should be constrained not allow a
> hierarchical address space to a universal resource simply because the active
> agent in the URI happened to be a script - the supplier of a resource in a
> REST environment should be invisible to the resource requester imho, however
> it is built under the surface of the request, I think it should just be
> /a/path/on/the/web and not a?subject=path&relation=on&article=the&object=web
> :)
> 
> but yeah, I should take that up with them.
> 
> On Wed, Dec 15, 2010 at 9:33 AM, Mark Thomas <ma...@apache.org> wrote:
> 
>> On 15/12/2010 14:03, Gary Lawrence Murphy wrote:
>>> On Wed, Dec 15, 2010 at 4:54 AM, Mark Thomas <ma...@apache.org> wrote:
>>>
>>>> Go read the spec. The JSP Servlet is mapped *based on file extension*
>> not
>>>> path.
>>>
>>>
>>> heh, how very quaint.  Where did they get this idea?  from MSDOS? Oh
>> never
>>> mind.  I don't think I want to know, and I suppose I just should be happy
>>> the names aren't constrained to 8 ascii chars.
>>
>> If you want to lobby the Servlet Expert group to modify the mapping
>> rules to support more flexible mapping then the place to send your
>> comments is jsr-315-comme...@jcp.org
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to