WISE Syncronization Logic
(→Example) |
|||
| Line 8: | Line 8: | ||
* Next the devices start a server service and wait for clients. If no client tries to connect within a wait time the device sleeps again and tries to find a server again. The server's wait time varies randomly between MIN time and MAX time. | * Next the devices start a server service and wait for clients. If no client tries to connect within a wait time the device sleeps again and tries to find a server again. The server's wait time varies randomly between MIN time and MAX time. | ||
* The ramdom times should cause the devices to be in a condition where one device is running as a server and another is running as a client. | * The ramdom times should cause the devices to be in a condition where one device is running as a server and another is running as a client. | ||
| + | * A [[WISE Protocol|syncronization]] is then run between the devices | ||
[[Image:WISE_17.png]] | [[Image:WISE_17.png]] | ||
== Links == | == Links == | ||
Revision as of 16:18, 10 April 2008
Timing
- Every device sets the time frame when it is available for syncronization by setting the start time and duration.
Example
- In this example every device has the same starting time for syncronization. Each device starts the process by running as a client and searching for available servers.
- None of them finds an available server and sleeps for a while (random time between MIN time and MAX time).
- Next the devices start a server service and wait for clients. If no client tries to connect within a wait time the device sleeps again and tries to find a server again. The server's wait time varies randomly between MIN time and MAX time.
- The ramdom times should cause the devices to be in a condition where one device is running as a server and another is running as a client.
- A syncronization is then run between the devices
