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 implemented as a separate thread. That thread will live short time or less: ... - ask partner "start independent VNC Server", - waiting of the reply (no more than 10 seconds), ... - connect to VNC Server via Tunnel, - waiting of the connection's result (no more than 20 seconds), ...
The above algorithm is based on the following data: 1) flag *VNC Server running?*, 2) flag *Auto-Start enabled?*, 3) flag *Tunnel-Only enabled?*, 4) flag *Direct or Tunnel*. The first step which algorithm do - it checks #1. But #1 doesn't is a "run-time" data (though #2-#4 is a "run-time" data). Some time ago when Kaboodle start at first time it processed "VNC running auto-detection". Or when the user push button "Check again" Kaboodle processed "VNC running auto-detection". At long term it is possible raise reliability to that data: Every time when Kaboodle started, it checks VNC running at its PC. That data (VNC running or not, and number of port if running) is added in the NID and all LAN PC use that. -Igor. ----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]> To: "Igor Kotelevsky" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 8:46 AM Subject: Re: VNC Server Status column > Igor: > Flow-chart attached. Looks much clearer to me now. :) > > -Scott > > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
