Adam, [snip] > 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. [snip]
FWIW, I think you're confusing the Tight encoding, which is just another image-encoding scheme, with the Tight pseudo-Security-Type, which is used to indicate that the two parties support custom protocol elements from the TightVNC project. HTH, -- Wez @ RealVNC Ltd _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
