The direct push technology keeps a device synchronized with data on a NotifyLink server offering the end user faster message delivery.
The direct push technology is implemented with software components residing on both the NotifyLink device client and on the NotifyLink server:
• NotifyLink Device Client. The device manages the direct push communication with the NotifyLink server. It establishes an HTTP or HTTPS connection with the server for a specified length of time, and then goes into an energy saving sleep mode while waiting for the server to respond. Server response indicates that new items were received or that no new items arrived. Based on this response, the device sends either a synchronization request or another direct push request. The continuous requests by the device each time the server responds, keep the connection from timing out between updates. The request transmissions are referred to as “heartbeats.” Each heartbeat serves to alert the server that the device is ready and still available to receive updates.
• NotifyLink Enterprise Server (NLES). On the NotifyLink server, the direct push component delivers e-mail and PIM (contact, calendar, and task) updates to a device as soon as the information arrives at the server using IP-based notifications. The persistent HTTP/HTTPS connection provides the means for up-to-the-minute synchronization for the end user.