canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
Loop/Architecture/Data Channels: Difference between revisions
Jump to navigation
Jump to search
→Format of Data: Add info on the contentType
(Initial version of data channel document) |
(→Format of Data: Add info on the contentType) |
||
| Line 21: | Line 21: | ||
Data sent across the data channel should be encoded in standard JSON format. Implementations should not fail if additional fields are sent within a message. | Data sent across the data channel should be encoded in standard JSON format. Implementations should not fail if additional fields are sent within a message. | ||
It is envisioned that all Loop messages for a data channel will have a contentType field specifying the type of message. Hence the message may be ignored if the contentType is not supported. ''It may be necessary in future to add a feature detection capability.'' | |||
Individual data types have their own structures. | Individual data types have their own structures. | ||