I have been working with the networking code and some volunteers
to track down the networking problems. The results are not completely
ready yet, but, since this problem has been lingering for a year or
more, I want to report some progress.
The short story is that networks and packet clusters out grew the
a couple of design decisions made years ago in WL networking, and
it took quite a few reports to convince me that code that had been
working for years had suddenly quit working. Its now clear that
it wasn't really sudden, except that the introduction of a tcp/ip
version caused the symptoms to be much worse because of its higher
speeds.
We are working on a solution, but I can't promise exactly when it
will be available. It will be availble when the testing works
well enough, and it will be in version 10.57.
Wayne, W5XD
A couple of details:
The bug in the inifinite gab cycle is verified and fixed.
There was a similar one in the network frequency display--not
reported as such, but just as much a problem for network bandwidth.
When joining a network in progress, all the QSOs in the log get
added to the local bandmap--this is a major problem if the log
has 10000+ QSOs.
An endless cycle of bandmap messages on the network could be
triggered by any of a number of circumstances--one of which is
adding a station to the network with more than a few dozen
QSOs to exchange with the network--all those QSOs ended up
on every station's bandmap, which is a problem.
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|