I was not suggesting to tunnel over your server, but to your server. Your server already contains a control infrastructure. If you'd go this route, your server would translate your proprietary protocol into VNC commands and back. Depending on the complexity of your protocol, this may be easier or harder than re-implementing and maintaining your entire client (which, as far as I understand, is mostly equivalent to a VNC server but using a different protocol) on the Mac side.
That would be almost impossible: a session is running with 8 https clients communicating to the server. The server has to have certificate that can be checked continuously at the certificate authority. It's a complete different model than all existing software and is mainly used by large enterprise clients. Some need a very high secutity level (banks) and we even need to write special servers for them.
Believe me: they won't take VNC for an answer. Paul _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
