W3C home > Mailing lists > Public > uri@w3.org > August 2009

Re: [Uri-review] ws: and wss: schemes

From: Erik Wilde <dret@berkeley.edu>
Date: Sat, 15 Aug 2009 22:25:49 -0700
To: Julian Reschke <julian.reschke@gmx.de>
Message-Id: <9D0A2154-6D08-4ABC-B6CE-3A7AA2FF8ACD@berkeley.edu>
Cc: Ian Hickson <ian@hixie.ch>, Greg Wilkins <gregw@webtide.com>, Maciej Stachowiak <mjs@apple.com>, Chris Anderson <jchris@apache.org>, Mark Nottingham <mnot@mnot.net>, Pieter Hintjens <ph@imatix.com>, David Booth <david@dbooth.org>, Kristof Zelechovski <giecrilj@stegny.2a.pl>, Jamie Lokier <jamie@shareable.org>, David Orchard <orchard@pacificspirit.com>, "noah_mendelsohn@us.ibm.com" <noah_mendelsohn@us.ibm.com>, "Daniel R. Tobias" <dan@tobias.name>, "uri-review@ietf.org" <uri-review@ietf.org>, "uri@w3.org" <uri@w3.org>, "hybi@ietf.org" <hybi@ietf.org>
On Aug 14, 2009, at 0:39, Julian Reschke <julian.reschke@gmx.de> wrote:
> Ian Hickson wrote:
>>>>   URI scheme semantics.
>>>>      The only operation for this scheme is to open a connection  
>>>> using
>>>>      the Web Socket protocol.
>>>>
>>>>   Encoding considerations.
>>>>      UTF-8 only.
>>> What does this mean?
>> That the only encoding that can be used with this scheme is UTF-8.  
>> What is unclear?
> You can only have ASCII characters in a URI. I believe you're trying  
> to do the right thing, but it really requires a few more words  
> (...when non-URL characters are to be used in a ws URI, they need to  
> be encoded using UTF-8 and then percent-escaped...)

i think there is some misunderstanding here: "encoding" here refers to  
the encoding of the URI (as julian has pointed out in his response),  
not the encoding of the payload of the protocol that is used to  
interact with resources identified by the URI.

cheers,

dret.
Received on Sunday, 16 August 2009 05:29:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:42 GMT