Fixed.
xFx already has a built-in mechanism via the config file to limit the
range of ports it looked at as I had thought there might be a problem
like this. This feature is somewhat redundant.
I have additionally randomised the new base port level it starts
looking at so there is much less chance of a clash. Saves lots of
try/fail/try/fail attempts at start-up in the presence of other xAPps.
Maybe somebody thinks this is another bad idea?
I only changed two values (the starting point for the free port scan
and the limiter) so I don't have any concerns over code stability.
S
--
Stuart Booth <<a
href="/group/xAP_developer/post?postID=RXVFiBCBeGBtXDX3N3y_Supyh6TrWcRrJXUQ7IWOuUgRMdRwBQ1bu1-RjzeJrXvnoaK3DdCfeOYrW-YLfA">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net
<a href="http://www.xapautomation.org/">http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/">http://www.xapframework.net/</a>
Comments to the Webmaster are always welcomed, please use
this contact form
. Note that as this site is a mailing list archive, the Webmaster has no control
over the contents of the messages. Comments about message content should be directed
to the relevant mailing list.