Oleg:
Another quick thought. I would think that the OpenSSH
project has some well designed socket interface code, as the
app is primarily used for tunneling. You *may* want to grab
that project's source and see what they've done.
-Scott
On Thu, 6 Dec 2001, Lyapin Oleg wrote:
> 06 dec 2001 Status report
> -----------------------------
>
> What we have done so far:
> =========================
>
> 1. We returned to two-machine scheme but there was one problem, which we did
> not solve but rather bypassed. Namely, the VNC server would not accept
> connection from it's own machine. This behavior is quite justified on normal
> conditions: you cannot VNC yourself. Our case is different: VNC Server
> should accept connection from Kaboodle on the same machine and in order to
> make it do so we just commented out a few lines of its code to bypass the
> checking and compiled a special version of VNC Server. The VNC Viewer we use
> is standard.
>
> 2. We changed the socket implementation to provide blocking and avoid
> delays:
> ---------------------------------------------
> Socket Was Become
> ---------------------------------------------
> VNC Server- CAsyncSocket WinApi Socket
> to-Kaboodle
> ---------------------------------------------
> Kaboodle- CAsyncSocket CSocket
> to-Kaboodle
> ---------------------------------------------
> Kaboodle-to- CAsyncSocket CSocket
> VNC Viewer
> ---------------------------------------------
>
> 3. Now, Kaboodle accumulates all bytes sent by other Kaboodle and being
> received by Receive function and only then forwards them to the VNC Viewer.
> Previously, the portions were forwarded immediately as they where received,
> which probably introduced some abuse.
>
>
> What we have achieved:
> ======================
>
> 1. The full VNC functionality is reproduced including screen image transfer,
> keyboard and mouse control. It still works slower then direct VNC connection
> but we have some thoughts to improve the output rate.
>
> 2. Both VNC Server and Viewer now are launched from within Kaboodle by a
> command line.
>
> What we are doing now:
> ======================
>
> 1. We will try changing the Kaboodle-to-VNC Viewer socket from CSocket to
> WinApi Socket. It has not been done so far because it proved to be more
> complicated than VNC Server-to-Kaboodle socket: Kaboodle must response a
> connection request rather then initiate one.
>
> 2. The VNC Server will start when Kaboodle starts provided the appropriate
> checkbox had been checked. The checkbox might be located on the Prosperity
> panel, tab System, next to the "Make this PC as the VPN node" checkbox. And
> to start the VNC Viewer a special button will be provided on the main
> Kaboodle window surface. It will be placed next to the "Disconnect" and
> "Prosperities" buttons, look the same and have the label "VNC Session". So,
> no special tab seems to be needed to control VNC activity.
> The solution with context buttons on the main window surface is probably not
> the best one but this approach has been developed by the Kaboodle team, so
> we tried to fit to it. I believe in the future this solution might be
> replaced by a falldown context menu activated by a right-click on a
> computer.
>
>
> PS: As for Igor, he is not planning to join the Kaboodle-Devel list right
> now because we work together and I write our common reports.
>
> -Oleg
>
>
>
>
> _______________________________________________
> Kaboodle-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
>
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
