Thanks for the information. I'm more than happy to eat crow, publicly, if VirtualBridges is using an openly documented API for their tech.
If their client/server model is at least compatible with traditional VNC clients that would be welcome news. I apologize for not seeing that earlier. If the claim in that pdf is accurate, and the protocal is at the very least openly documented that most definitely assuages the deepest of my concerns. Even if the server and client code they sell in that deal is closed, having an open API means that an open implementation for both the client and the server can compete in the marketplace which is the most important thing.
If you able to dig up any authoritative reference that documents the protocol extension or if you find their sourcecode repository, please let me know so I can make the appropriate retraction here, but also on my blog.