MobiLink Synchronization User's Guide
  Server-Initiated Synchronization

Deployment considerations

Following are some issues that you should consider before deploying server-initated synchronization applications.

Limitations of UDP Listeners 

• The UDP Listener keeps a socket open for listening, and so must be connected to an IP network all the time.

• The Listener does not detect lost connections and cannot re-open the listening socket.

• If you use dynamic IP addresses on the remote, you may have trouble updating the address on the server. MobiLink does not provide IP tracking. You may be able to use a third-party solution.

• The IP address on the remote needs to be reachable from the MobiLink synchronization server.

Limitations of Listeners on CE or PCs 

• The Listener requires that the operating system is running, which could result in battery drain. Make sure that you have enough power for your usage pattern.

Delivery not guaranteed 

• Both SMS and UDP delivery are not guaranteed, so you should implement a feedback loop if guaranteed delivery is essential. For example, you can use the MobiLink last_upload_time and last_download_time values to verify the delivery status of push requests.