- From: Hugo Haas <hugo@w3.org>
- Date: Mon, 1 Jul 2002 17:40:58 -0400
- To: www-ws-arch@w3.org
* Hugo Haas <hugo@w3.org> [2002-07-01 16:45-0400] > > As per my action item, I started reading SOAP version 1.2 Last Call > Working Drafts. > > Here are some architectural comments about SOAP Version 1.2 Part 1: > Messaging Framework. [..] Oops, I forgot one comment. 5) Comment: Length of URIs. I remember a somewhat long discussion on xml-dist-app about that and am still unsure about what we should say, but the following statement struck me[8]: | SOAP does not place any a priori limit on the length of a URI. Any | SOAP node MUST be able to handle the length of any URI that it | publishes and both SOAP senders and SOAP receivers SHOULD be able to | deal with URIs of at least 2048 characters in length. Even though the URI specification doesn't specify any limit on the length of a URI, the HTTP spec does provide a URI too long error code[9]. 2kB is identified here as a reasonable value to be able to handle. This seems to be an architectural issue, a Web services one as well as a Web one. I am afraid that such a statement will have a big impact on software designed. I think that I would be more comfortable by saying that software should be able to handle URIs of arbitrary length, and that a 2kB-length is seen _in SOAP's context_ as a minimum value to support. Regards, Hugo 8. http://www.w3.org/TR/2002/WD-soap12-part1-20020626/#useofuris 9. http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.15 -- Hugo Haas - W3C mailto:hugo@w3.org - http://www.w3.org/People/Hugo/ - tel:+1-617-452-2092
Received on Monday, 1 July 2002 17:40:59 UTC