SHARX SECURITY HTNC Series, Руководство по API, Страница: 122 / 228

Contents-Length: 20
fulltext=1&trigger=1
3) HTTP CONTINUES RESPONSE
HTTP/1.1 200 OK
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1234567890"
--1234567890
Content-Type: application/ht-event; charset="UTF-8"
Content-Length: 91
event_time=2014-12-02 20:03:47
trigger=0
trigger1=0
trigger2=0
trigger3=0
trigger4=0
--1234567890
Content-Type: application/ht-event; charset="UTF-8"
Content-Length: 91
event_time=2014-12-02 20:03:47
trigger=0
trigger1=0
trigger2=0
trigger3=0
trigger4=0
* Event Stream Server transmits Event information via HTTP response, and uses multipart
Content-Type boundary to differentiate Event Groups occurred at the same time.
* Each Event in an Event Group is differentiated by “\r\n”.
Event Stream Request Parameter
Request Parameter includes Channel number, Stream number, and Event Filter, and that
information determines the event type to receive.
The Parameter Format is ‘<parameter_name>=<value>’, and each Parameter is separated by ‘&.’
Table 1. REQUEST PARAMETER
Parameter Type Description Value
ch integer channel number default : 1
strm integer stream number default : 1
fulltext boolean Transmit event detail 1 : enable, 0 : disable
alarm boolean Transmit H/W Alarm-In event 1 : enable, 0 : disable
alarmout boolean Transmit H/W Alarm-Out event 1 : enable, 0 : disable
trigger boolean Transmit S/W Manual Trigger event 1 : enable, 0 : disable
netloss boolean Transmit Network Loss 1 : enable, 0 : disable
pir boolean Transmit PIR event 1 : enable, 0 : disable
audiodetect boolean Transmit Audio Detect event 1 : enable, 0 : disable