21 dec 2001 Status report ----------------------------- >1. What TCP port are you using for Kaboodle->Kaboodle for > secured VNC traffic?
Currently we use ports 4000 and higher, although it is not a matter of principle. You enter the desired port number in a special box. >2. How many sessions of VNC can simultaneously be carried > across this channel? I'm *really* hoping it's more than > just one... Today we put in on the test. We made two machines Kaboodle+VNC servers and one machine a Kaboodle+VNC viewer. As no native multi-session support had been designed yet, we manually set up the proper values of ports and VNC displays. We succeeded to run two sessions at time and control the servers simultaneously through two windows on the viewer. We believe there are no program limitations for the number of sessions, provided that the hardware and the network are good enough. >3. I'd be interested in hearing your figures for redesigning > the "steel tube" interface. Long term, it *must* work that > all traffic between two remote Kaboodle users is transacted > over a single TCP stream. It must carry Kaboodle "control" > info, VNC data, and be scalable to support an arbitrary > number of other bidirectional data "channels". We entirely understand the importance of having a single "steel tube" for all Kaboodle applications. We are sure that after the MFC sockets are replaced with pure WinAPI sockets, and some additional measures are undertaken to support intensive bi-directional data exchange, the resulting "steel tube" will be capable of carrying Kaboodle "control" as well as VNC and other Kaboodle applications. Commonly, WinAPI sockets are more fast-acting than MFC sockets. _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
