5.5. Polling

Polling is used by the client to manage notifications about relevant events in the Registry.

The relevant events are mostly those that are not triggered by the client, such as time-based events (expiration, deletion of idle objects), asynchronous responses (technical check results), events that are triggered by other registrars (transfer) or by the Registry itself (consequences of contacts’ merger).

The workflow is following:

1. The client orders the notification messages by issuing a poll request.

2. In response, the server informs about the status of the message queue (the message count), includes contents of the first (oldest) message and provides its identifier for acknowledgement.

3. The client is supposed to confirm the receipt of this message by issuing a poll acknowledgement with the identifier of the read message.

4. The server removes the acknowledged message from the message queue and responds with a new message count and the identification of the next message in the queue.

5. The previous steps can be repeated to read the remaining messages until the count is reduced to zero.

Note

The EPP standard allows to announce a non-empty message queue (<msgQ>) in response to any command, however the FRED EPP server gives such response exclusively to an explicit poll request.

• 5.5.1. Poll request
  • 5.5.1.1. Command element structure
  • 5.5.1.2. Response element structure
• 5.5.2. Poll acknowledgement
  • 5.5.2.1. Command element structure
  • 5.5.2.2. Response element structure
• 5.5.3. Poll message types
  • 5.5.3.1. Low credit
  • 5.5.3.2. Request usage
  • 5.5.3.3. Domain expiration
  • 5.5.3.4. ENUM domain validation
  • 5.5.3.5. Object transfer
  • 5.5.3.6. Object update
  • 5.5.3.7. Idle object deletion
  • 5.5.3.8. Domain deletion
  • 5.5.3.9. Technical check results