Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCWEB Data Channel: Usage of PPID for protocol multiplexing)

[Michael Tuexen <[e-mail]>]

On Feb 8, 2014, at 9:24 PM, Randell Jesup <[e-mail]> wrote:

> On 2/7/2014 6:45 PM, Martin Thomson wrote:
>> I don't think that we need any complication here.  It's a string.
>> 
>> Strings are UTF-8 on the wire.
>> 
>> Strings are UTF-16 (mostly) in JavaScript.
>> 
>> Anything else would generate pain.
> 
> (Back online while traveling; been off mostly due to extended power outage in Philadelphia suburbs)
> 
> 100% agree.  And currently that's what we do in Firefox at the JS->protocol interface:
> 
> void
> nsDOMDataChannel::Send(const nsAString& aData, ErrorResult& aRv)
> {
>  NS_ConvertUTF16toUTF8 msgString(aData);
>  Send(nullptr, msgString, msgString.Length(), false, aRv);
> }
> 
> The JS interface matches WebSockets Send().  The wireline interface is (and should be) UTF8; any registrations should be updated to make this clear.
Great. I'll update the spec. Let's change the name of the PPID...

Best regards
Michael
> 
> -- 
> Randell Jesup
> [e-mail]
> 
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb
>