Hello Adam, >>>>> Adam Tkac wrote:
> AFAIK the Tight encoding is a mechanism to encapsulate other > encodings thus you end with something like a "protocol inside > protocol" (The Tight encoding already has many sub-encodings like > FTP-like transfer related encodings and the JPEG encoding as you wrote > above). I really don't like such approach because it might end with > crippled and badly designed protocol. You are seriously mistaken. Tight encoding is just an encoding, not a "protocol inside protocol". It does not allow to encapsulate other encodings. Indeed, Tight encoding has subencodings (e.g. JPEG) but the set of subencodings is fixed and they are integral parts of the Tight encoding and just allow to encode data in different ways depending on the statistical properties of that data. TightVNC does not include anything like "FTP-like transfer related encodings". File transfers are implemented via TightVNC extensions to the RFB protocol, they do not use any encodings, they use new protocol messages. -- With Best Wishes, Constantin _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
