Nivis Versa Router 1100 Titan, Руководство пользователя

Страница: 41 / 111

Nivis Versa Router 1100 Titan - User Guide v1.2 Page 41 of 111
3.9.1.1.8.6 Retrieving data history
HTTP query: http://storage-data-get/(?device=device_ipv6_addr&since=time_since&until=time_until
&oldest/newest=N/path=resource_path )
Query may specify “device”
Query may specify “since”, “until”, both of them or none.
If query specified device one of “oldest”, “newest” queries may be specified.
Query may specify a “path” containing a target resource path.
HTTP response:
If request is well formed, HttpCoapProxy will retrieve an XML with history data which is stored for
device_ipv6_addr device, from time_since and until time_until ; time_since and time_until must be
specified in UNIX timestamp format. If both “since” and “until” queries are missing, will be retrieved an
XML with all history data which is stored for
device_ipv6_addr device; this initial XML report will contain
a number of X records. If “oldest” query is specified, the XML report will contain only first N records
from X (or X if N >X), which represent the oldest records from the initial report. If “newest” query is
specified, the XML report will contail only last N records from X (or X if N >X), which represent the
newest records from the initial report;
If path is specified, the proxy will perform a search using the provided path filter.
If no device_ipv6_addr is provided, the proxy will provide the history for the entire storage.
If no device_ipv6_addr is provided, “oldest” and “newest” queries do not apply.
If storage for device_ipv6_addr device doesn’t exist, “Storage not found” response will be retrieved;
If request is not well formed, 400 "Bad Request" response will be retrieved, with the information
“Storage-data-get request is bad formed”.
Each record from the response XML has the following form:
<Record>
<uriPath>Path</uriPath>
<e t="timestamp"><Application v="value"/></e>
</Record>
If device is provided, the response XML will have the following form:
<DataRetrieving>
<Record>
<uriPath>path</uriPath>
<e t="timestamp"><Application v="value"/></e>
</Record>
…
<Record>