Black Box Version 1.0 Manual de usuario descargar pdf (Pagina 13)

Client Initial Connection

• Simple “status” message

• Identifies self via UDID

• Triggers server to provide command

<dict>

<key>Status</key>

<string> [ redacted ] </string>

</dict>

</plist>

Command Format

• Command in “RequestType” field

• CommandUUID field mandatory

–Content optional

–Allows matching of commands and responses

<dict>

<key>Command</key>

<dict>

<key>RequestType</key>

<string>ClearPasscode</string>

<key>UnlockToken</key>

<data>[ redacted ] </data>

</dict>

<key>CommandUUID</key>

</dict>

Now that the device is fully enrolled, it can respond to push notiﬁcations

by contacting the “Server URL” address. When connecting, the client

PUTs a simple message identifying “Status = Idle”, and the server

responds with a command, again in a .plist format.

The client executes the command, and responds with a simple

acknowledgement message, or with appropriate data as requested by

the server.

The commands are framed in .plist format. A top-level key “Command”

is made up of a dictionary of key/value pairs. Usually this will include

only the single key “RequestType,” which has as its value the actual

command being sent. In some cases, additional parameters will get

added as peers to the RequestType key.

The command also includes a UUID string that uniquely identiﬁes the

instance of the command. This is useful for matching up responses with

the command that caused them to be sent, especially when several

commands may be queued up but aren’t necessarily delivered, or

processed, in order.

In practice, this ﬁeld can actually be left blank, however it’s probably

best practice to ﬁll it with some random (or controllable) UUID.

1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 30 31

Comentarios a estos manuales

Sin comentarios

Black Box Version 1.0 Manual de usuario Pagina 13

Comentarios a estos manuales

Relacionado con productos y manuales para Redes Black Box Version 1.0