Skip to content
David O'Rourke edited this page May 24, 2018 · 3 revisions

Presentation (Layer 6)

Each distinct Torpedo protocol is identified by a 4-character appId. The appId is encoded in the header of the message, and an application may use the appId to filter its interest in received messages. For any given appId, there should be a well-defined format for the body of the message.

The following protocols are currently defined

TEXT an unaddressed raw unicode text string
MESG an addressed unicode text string
PTCH an addressed json object usually used to represent module settings
Clone this wiki locally