Re: Case-sensitivity of PLT web server

[Kirill Lisovsky <lisovsky@acm.org>]

Hello!

On Thu, 18 Apr 2002, Paul Graunke wrote:
> For (c), you can change your servlet from
>
> (unit/sig () (import servlet^) ...)
> to
> #cs(unit/sig () (import servlet^) ...)
> where the #cs stands for "case sensitive".
> 
Thank you, it works.

Is it possible to make case sensitive behavior predefined for servlets?

Otherwise #cs will be a FAQ, and its omission - a popular reason for errors.
For XML-related apps. I can predict this for certain...

> I just tried this and it produced case sensitive tags for me. I think
> it's best that code that depends on case sensitivity (or lack there of)
> specifies which it requires. Depending on the particular instance of
> mzscheme's default might make it hard to combine code from different
> developers.
>
Actively using Scheme as XML processing language I've never seen a practical 
example of Scheme code which _depends_ on case insensitivity. 

What I _have_ seen (especially in IT) is confusions and questions...
This trivial issue is a reason for disproportional amount of troubles.

IMHO, case sensitivity is _required_  for some application areas 
(XML in particular), while case insensitivity is mostly a tradition.

An attempt to combine them leads to bar notations, command line switches / 
preferences, different predefined modes for different Schemes (in PLT - 
even for different languages), (string->symbol "Ab") approach, different
readers, #cs and alike, and more ...

Is it worth such efforts considering cost/benefits?
I dare say that for XML/Scheme application domain the answer is negative...

Well, I do sorry for some offtopic. 
It was a long discussion on case sensitivity on comp.lang.scheme
a year ago (I believe it's available via google), and I don't want to start 
a new one.

> Let me know if this resolves the issue to your satisfaction.
> 
Thank you a lot for fast and exhaustive reply!
#cs allows to write a case sensitive servlet.

Please consider the request for ultimate solution:
case sensitive web-server out of the box.

IMHO, it will:
 1. simplify deployment of webserver-based solutions
 2. increase their robustness
 3. prevent upcoming questions on the subject :-)

Best regards, 
         Kirill.