Hello James, Brian, >>>>> "p" == "\(n/a\)" <[EMAIL PROTECTED]> writes:
p> I get "Terminate Connection ZlibHex unknown subencoding 113 p> encountered" error message. I think the standard RFB protocol specification (in particular, the 3.7 version) clearly states that: In addition to genuine encodings, a client can request a "pseudo-encoding" to declare to the server that it supports a certain extension to the protocol. A server which does not support the extension will simply ignore the pseudo-encoding. Note that this means the client must assume that the server does not support the extension until it gets some extension-specific confirmation from the server. Why not to treat ZlibHex (or Tight, or anything else) just as a "pseudo-encoding" in that context?.. But I think the problem in this case is that a certain VNC client does know ZlibHex encoding, but cannot decode it correctly (note "ZlibHex unknown _subencoding_"). I guess that's a problem with a specific encoder/decoder, and it has nothing to registered encoding numbers, correctness of any replies in the VNC mailing list, any PR activities or politics in general. -- With Best Wishes, Constantin _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
