Commit 1120c4fd authored by Peter Waher's avatar Peter Waher

Adding notes.

parent 4109fd64
......@@ -16,8 +16,9 @@ XMPP supports three Publish/Subscribe communication patterns:
**Note**: The Publish/Subscribe pattern might be an efficient way to distribute sensor data to many subscribers. But it comes at the price of flexibility and
privacy. Only use the Publish/Subscribe patterrn from devices that actually have many subscribers, and in cases where data does not need to be tailored for
individual receivers, such as is the case if using provisioning on a field level. The Publsh/Subscribe pattern also leaves little room for subscribers to tailor
under what circumstances they want to be updated. In all these cases, the [Request/Response](SensoDataRequestResponse.md) or
[Event Subscription](SensorDataEventSubscription.md) patterns might be more efficient.
under what circumstances they want to be updated. Note also that the data is processed and persisted on the broker (to some extent). End-to-end encryption is
not supported. If privacy, flexibility or customization are concerns, the [Request/Response](SensoDataRequestResponse.md) or
[Event Subscription](SensorDataEventSubscription.md) patterns might be more suitable. They also place less load on the broker if there are few subscribers.
In all three cases, [sesor data](SensorData.md) is represented using the same XML representation as used in the other sensor data related
communication patterns.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment