-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gary,

On 12/15/2010 11:24 AM, Gary Lawrence Murphy wrote:
> http://host:8080/clock/thetimeis.now/utc
> 
> what I am hearing in the thread here is that I have introduced a
> CPM/MSDOS convention from the middle 70's that now changes the URI
> from a valid expression into an invalid one.

Then you aren't listening. The presence of a dot is not relevant: it's
just another character. The servlet specification lays out 4 kinds of
pattern matches. You're right, though, that they only allow globbing for
"extension mapping" which might cramp your style.

There is also this note in the 3.0 spec:

"
Versions of this specification prior to 2.5 made use of these mapping
techniques as a suggestion rather than a requirement, allowing servlet
containers to each have their different schemes for mapping client
requests to servlets.
"

So, not only have the authors restricted mapping to a certain set of
patterns, they have made it mandatory how they are processed. If you
read the spec (hint, hint), you'll see that any other behavior is
actually prohibited by the specification. Complaints can be sent to
those responsible.

> That is the issue I struggle to understand and I will re-read that
> spec a few times, but on the first two readings I do not find any
> rule that demands that the active server trigger term of the URI must
> needs be the terminal token *iff* that token contains a
> servlet-mapped CPM/MSDOS extension suffix routing to a script
> interpreter.

Can you show us a url-pattern that meets the spec that gives you what
you want? Note that "extensions" are not limited to 3 characters...
there's no reason to blame MS-DOS for anything (at least not here).

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0I8VAACgkQ9CaO5/Lv0PDqGACgw3R4V1q5z7zflUPJ+HfqPZm1
As0An0Z4udYNxKOZeIWbdWD4nsp3QKPM
=M9f2
-----END PGP SIGNATURE-----

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

Reply via email to