I've read some of the threads regarding synchronizatrion of serial
numbers, and I have a small suggestion.
The logic behind synchronization is to send a unique incremental serial
number to a new station.
The solution to acquire this logic is actully quite simple,
programatically and theoretically.
Consider the following setup:
Station A (RUN) - Computer (A)
Station B (MULTI) - Computer (B)
Station A is running band A, while stattion B is picking multis on band
B.
The contest in context has defined the following rule:
Multis can be picked in a SINGLE-MULTI operation as long as the MULTI is
new to all bands.
---
The problem with WR 10.62 (I don't have the latest version yet) is:
- Station A has a pileup and is a fast operator
- Station B is an OM, and not so fast. He's enjoying picking multis.
Typing is also not his native language HI.
WR on the RUN station will lock a serial number, for instance 155.
Station B has at the same time (before station A logs the QSO) picked up
a new multi and starts typing, he receives the same serial number.
While station B is typing, station A sends 155 and logs the QSO.
At the same moment, station B sends 155 and logs the QSO.
We now have duplicate serial numbers.
---
Solution:
All serials are unique. There is no chance whatever that two stations
will acquire the same serial number.
Serial numbers are incremental.
If either of the stations do not log the QSO, the output is one of two:
- The serial is not reused
- The serial is reused.
---
The setup requires a small fraction of server software.
This software is implemented as part of WR, and the RUN station will be
the dedicated server.
The server maintain the serials, and synchronize the clocks.
---
with Regards
Filip Poverud - LB1UE
lb1ue@qrz.no
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|