Den 2009-06-11 12:15 skrev Daniel P. Berrange:
> On Thu, Jun 11, 2009 at 11:15:14AM +0200, Peter Rosin wrote:
>> Having a security type named UTF-8, which simply allowed the client
>> to select the "real" security type right after it would perhaps not be
>> so difficult.
>
> I've never much liked the idea of stealing security types to negotiate
> non-security related features myself. It is pretty trivial to implement
> the DesktopName encoding. So if we did it with a pseudo-encoding, the
> serverinit message would still be ASCII, but would recommend that the
> server send a DesktopName message with the UTF-8 encoded name version.
Right, the UTF-8 extension as a pseudo-encoding is adequate. +1
Question is if this UTF-8 extension should affect anything other than
the ServerInit and {Client|Server}CutText messages.
I.e. should DesktopName be assumed to be ASCII only until UTF-8 has
been seen by the client or should DesktopName always be UTF-8?
Or should we just leave the DesktopName encoding unspecified until
UTF-8 has been seen?
Cheers,
Peter
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
tigervnc-rfbproto mailing list
tigervnc-rfbproto@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-rfbproto
