From 2450d93cc395e1201bb3c2d15b41a369674bfe6b Mon Sep 17 00:00:00 2001 From: akwizgran Date: Fri, 24 Apr 2015 17:53:05 +0000 Subject: [PATCH] Blog signature must cover the client ID --- TransportClient.markdown | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/TransportClient.markdown b/TransportClient.markdown index 0f9f619..288dcc1 100644 --- a/TransportClient.markdown +++ b/TransportClient.markdown @@ -2,16 +2,18 @@ TransportClient is a [BSP client](BSP) that synchronises transport properties be ### Channel identifiers -TransportClient has a single channel with the following random identifer: +TransportClient uses the following client identifer: `673e a091 6735 61e2 8f70 122f 6a8e a8f4 97c3 624b 86fa 07f7 85bb 15f0 9fb8 7b4b` +The client uses a single channel for all messages. The [client data structure](BSP#channel-identifiers) for the channel is a [BDF list](BDF) with a single element: "UPDATE" (string). + ### Message types -**0: UPDATE** - The content is a [BDF](BDF) list with three elements: `transport_id` (string), `version` (int), and `properties` (dictionary). `transport_id` and `properties` are supplied by the transport plugin. `version` is incremented whenever the properties change. +**0: UPDATE** - The content is a list with three elements: `transport_id` (string), `version` (int), and `properties` (dictionary). `transport_id` and `properties` are supplied by the transport plugin. `version` is incremented whenever the properties change. ### Validity policy -* An UPDATE is valid if it is well-formed. +* An update is valid if it is well-formed. ### Storage policy