Re: Request for allocation of RFB message types for TightVNC
Hello Tristan, > Tristan Richardson wrote: > Our current policy is to allocate to third parties the high message > numbers (i.e. 255 downwards), so can I suggest you use 252 for both > server->client and client->server. Ok, thank you. -- 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
Re: Request for allocation of RFB message types for TightVNC
Hi Const, Our current policy is to allocate to third parties the high message numbers (i.e. 255 downwards), so can I suggest you use 252 for both server->client and client->server. Cheers Tristan Constantin Kaplinsky wrote: Hello, I'm writing here in order to reserve RFB message types that will be used in TightVNC. I need one client-to-server message and one server-to-client message as well. Please allocate equal numbers for both messages if possible. ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
Request for allocation of RFB message types for TightVNC
Hello, I'm writing here in order to reserve RFB message types that will be used in TightVNC. I need one client-to-server message and one server-to-client message as well. Please allocate equal numbers for both messages if possible. -- 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
