There are still a couple of string issues remaining: - SecurityResult doesn't mention encoding for reason-string. It should probably be ASCII though, which is what is specified for reason-string in Security.
- Tight's capability handshake uses something that looks like strings, but should be handled like opaque, 8 byte blobs (or so I'm assuming). Perhaps this should be clarified? - The GII stuff doesn't mention anything about encodings for its strings. If it's undefined then we should refer to the new encoding chapter. Rgds -- Pierre Ossman OpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio AB Web: http://www.cendio.com
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________ tigervnc-rfbproto mailing list tigervnc-rfbproto@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-rfbproto
