Igor:
> I see a principle conflict between "VNC auto-detection" and the option
> "Tunnels only".
> If Kaboodle has the option "Tunnels only"
> then VNC registry setting has the value "LoopbackOnly = 1".
> In that case VNC Server rejects all socket requests from alien IP address.
> As result "VNC auto-detection" cannot complete successfully.
That's a really good point.
> Here is what I have implemented.
> ...
> Every time when Kaboodle starts,
> it put above information into the itself member _NID_DEVICE_ATTRIBS.
> That data is part of NID update.
> Kaboodle checks that data when it comes.
> As result we have not only elimination of above conflict,
> but increasing of validity of independent VNC Service information.
> If Kaboodle receives that data from device PCn,
> it doesn't performs "VNC auto-detection" for device PCn at first start up.
That's a really good idea. As per my earlier email, I think
all device attributes *except passwords* should be put into a NID update
like this one.
> The size of NID update data has increase now (4 bytes * number of
> devices). As I know Kaboodle doesn't has a defensive remedy for that.
> Please don't start old and new version simultaneously.
You're right: the old versions now crash when they are started
up into a LAN that has the new version running.
-Scott
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
