Thanks for the update. Comments inline:
> 1)
> While attempting to reduce the new development efforts by using
> existing code to check tcp port free condition I've discover:
>
> file: Common\tcp_service.cpp
> methods: bool TcpService::IsFreeServerTCPSocket(UINT uiPort)
> bool TcpService::IsAnyTCPListner(DWORD dwIpAddress, UINT uiPort)
> Malfunction:
>
> These functions implement wrong algorithm to check
> is TCP port free. They assume: if we can connect to
> server socket then listener exists and port is busy,
> and if we can't then port is free,
A clever algorithm.
> BUT:
> we could get fault to connect when port is busy, but
> is overloaded.
Have you seen this bug?
> So I am enforced to write a brand new method to check tcp port free
> condition. This method is based on getting the system tcp table where
> all used tcp ports are listed.
That's a good approach too. But if you've never seen the
bug, is it really a bug? We could, say, check to see if a port
is busy using the original algorithm twice or three times. Or if
writing the new method is only a few hours work, that's fine too.
> Regarding VNC server restart steps. You offer:
> 3.4 When the user presses the "Start Now" button, Kaboodle
> should first try to stop any VNC Servers running, either
> Service or App modes. Note: the current code looks like
> it's doing this already.
>
> 3.5 Once Kaboodle has stopped all detected VNC servers, it
> should try to detect if the port it's about to use is
> free or not. If it's not free, Kaboodle should put up a
> MessageBox warning: "Sorry...Kaboodle cannot start VNC on
> that port, as it is already in use by another application".
> In the current code, Kaboodle first tries to start the VNC
> server, and *then* checks for success. If the check fails,
> Kaboodle reports in a MessageBox: "Failed to restart WinVNC
> on port number ####. That port may be in use by another
> application..."
>
> But I think it would be better first to get sure that the new port is
> free ( as the server path also ) and only after this kill current VNC
> server. If user enters bad new valuAes what for we will stop current VNC
> server?
Of course, you're right. Good point.
> 2)
> Detectable abnormality:
>
> While Kaboodle.exe is loading some dark box (color of background) is
> appearing twice near "Somobody's Network" icon. I think it is some wrong
> appearing message. It looks like demonstrable bug. Have you got
> something like this?
I've not seen this bug, no. But I have seen Kaboodle take
~10 seconds to startup (ie, display it's initial GUI) on a very-new
Win2K P4 before.
thanks,
Scott
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
