User`s manual

Automatic Response Pushing

The gateway can be configured to push responses immediately to the iDigi server

instead of the default polling mode via RPC_response. (See “RPC_Manager.use_push”

on page 46.) Memory on the gateway is limited and it can be advantageous to store

responses on the iDigi server to avoid the risk of dropping messages if too many

responses are generated.

Note: Response messages will not be removed from the gateway’s buffer until they have been

successfully pushed to the iDigi server. Responses can still be retrieved via RPC_response if

pushing does not succeed for any reason.

File Format

Each pushed file contains a single response without any RCI or SCI wrapper.

You must bring us another shrubbery.

</description>

</message>

The filename is formatted with the following information; pushed file prefix (defaults to

RPC_response), timestamp, sequence number, response type, and file extension

(defaults to xml). The sequence number differentiates responses pushed in the same

second.

RPC_response-1234567890-0000-message.xml

RPC_response-1234567890-0001-get_version_response.xml

RPC_response-1234567890-0002-get_device_information_response.xml

RPC_response-1234567891-0000-message.xml