# QUEUE-READ Request

Function

QUEUE-READ requests are used to collect or read messages from the message queue of the RRI from the RegAcc.

Requirements

Messages can only be output if the total number (MsgCnt) of messages in the message queue is not 0.

Special Features

- With a request, only one message is requested, regardless of the total number of messages in the message queue.
- By specifying a message type, a specific message can be requested.

Reading Messages

General

Example: A RegAcc sends a QUEUE-READ request to the RRI.

- There are 3 messages in the message queue,
  - 2 of type “expireWarning”,
  - 1 of type “authInfoExpire”.
- The “authInfoExpire” message is the message with the oldest date.

Result: The message with the oldest date, i.e. “authInfoExpire”, is output.

Specific

A specific message type can be issued by specifying the keyword “MsgType” followed by the message type, e.g. “expireWarning”. If there are several messages of a type in the message queue, the message with the oldest date is issued.

Automatic Reminders for Older Messages

- If messages in the message queue are older than three days, the RegAcc is automatically informed. This is done by sending an e-mail to the “EMailTo” address from the RegAcc profile.
- The notification e-mail is sent once a day if the messages remain in the message queue (and are older than three days).

K/V Keyword | XML Namespace and Element | Occurrence min - max | Type / Length | Value Range | Description
--- | --- | --- | --- | --- | ---
Action | queue-read | 1 | enumeration | queueread-erule | request type
Version | - | 1 | enumeration | version-erule | version, only relevant for requests in key/value format
MsgType | msgtype | 0-1 | enumeration | msgtype-erule | type of message; if no MsgType is specified, the oldest message (sorted by MsgTime) is displayed