Hello Scott.
Your *Flow-chart attached* is perfectly specified. Thanks.
(Sorry, I got accustomed to use secret channel for secret goal and usual
channel for usual goal. Therefore I could not to understand algorithm
early.)
I will implement this algorithm.
It seems to me that algorithm must be impl
Igor:
Flow-chart attached. Looks much clearer to me now. :)
-Scott
VNC_flow.GIF
Description: GIF image
Igor:
> > 1. Whenever a VNC connection through a Kaboodle tunnel fails,
> >Kaboodle should try to connect again directly before reporting
> >failure to the user.
> We have to remember that Kaboodle cannot to verify success of VNC direct
> connection.
> VNC is independent application and i
Hello Scott.
Thank you, I had a good weekend, hope that you too. My comments inline:
> Keep in mind that Kaboodle can startup the VNC server
> for both tunneled and direct connections. So I see the flow like
> this:
>
> 1. Whenever a VNC connection through a Kaboodle tunnel fails,
>Kaboodle s
Igor:
Heya. Hope you had a good weekend. Some comments:
> Hello Scott.
> Now button "Connect" for PropertyTab "Vnc Settings" of icon "VNC
> service" works as following.
> User on PC1 selects PC2 and push "Connect".
>
> 1) - If the user on PC2 has "Connect Directly" and PC2 is running
> i
Hello Scott.
This is our common message(from Oleg and Igor).
Some words about usual Kaboodle messaging (below referred as UKM).
UKM is implemented as separate thread.
Current code posts messages to that thread and doesn't check result of
really sending data via socket connection.
If socket connec
Igor:
You're right: the usual Kaboodle messaging doesn't have
any documentation. Right now, it's used for NID updates (ie, when
I change a device name in one Kaboodle window, all of the Kaboodle
instances on the LAN will get updated). Long term, I'll be changing
how Kaboodle sends these up
Igor:
Yes, Kaboodle needs to be able to send a special message
to another Kaboodle telling it to startup a regular VNC service.
I was thinking this could fit into the usual Kaboodle messaging
going on, rather than require a dedicated TCP port listener.
-Scott
On Tue, 14 May 2002, Igor Ko
Hello Scott.
You wrote:
> 2. If no independent VNC service is running and Kaboodle on PC1
>has "Kaboodle starts VNC" selected and the server field is
>non-empty, then the the status column in Kaboodle on PC2
>should say "automatic". If the Kaboodle user on PC2 hits
>Connect, then K
Igor:
Hello! Some feedback on your ideas:
> > > Status column will be
> > > a) "active" when #2;
> > > b) "automatic" when no #2, simultaneously #1 with both options "Enable
> > > Kaboodle Tunnels for VNC"
> > > and "Let Kaboodle auto start and restart the VNC Server when it needs
> > > t
Hello Scott.
First. About the value of status column.
Igor wrote:
> > What now will show ProperyTab "Viewer Settings"?
> > May be it is list of all LAN PC which
> > 1) running Kaboodle or
> > 2) running independent VNC Server.
> > Status column will be
> > a) "active" when #2;
> > b) "automatic" w
11 matches
Mail list logo
