If a new version of HTTP specifies the use of ';' rather than '', the
servlet engine could detect the HTTP version and decode appropriately.
What I don't understand is why it's a "problem" for HTTP at all, since it
seems to work just fine right now. I don't think it requires a new HTTP
version
David Wall wrote:
If a new version of HTTP specifies the use of ';' rather than '', the
servlet engine could detect the HTTP version and decode appropriately.
What I don't understand is why it's a "problem" for HTTP at all, since it
seems to work just fine right now. I don't think it
David,
Good question.
If a new version of HTTP specifies the use of ';' rather than '', the
servlet engine could detect the HTTP version and decode appropriately.
Personally I'm not holding my breath. So many existing programs, CGI and
otherwise, depend on ampersand-separated arguments, it
-
From:
David
Wall
To: [EMAIL PROTECTED]
Sent: Friday, November 19, 1999 10:27
AM
Subject: Using for params in
URLs
Everything I read related to HTML 4.0 is that the to
separate parameters (based on the older CGI convention) has been deprecated.
The W3C suggests
-
From:
Taylor
Gautier
To: David Wall ; [EMAIL PROTECTED]
Sent: Friday, November 19, 1999 4:43
PM
Subject: Re: Using for params in
URLs
Umm, no, to be honest I have never heard of such a
thing.
It sounds as if you are referring to URL's, and I don't
