Download Diffusion 5.5 User Guide - Documentation

Transcript
Note: Some APIs do not support all of these encodings. For more information, see the
API documentation.
Transport capabilities
When a client connects to the Diffusion server, the server establishes whether or not the
connection has the capability to support the encodings. If the connection can support the
encoding that is specified for a message, the Diffusion server applies that encoding to the
message. If the connection does not support the encoding, the message is transmitted
unencoded.
The following table lists the encodings supported by each transport:
Table 10: Encoding support transports
Transport
Compressed
Encrypted
Base64
DPT
YES
YES
YES
WebSocket
NO
NO
NO
HTTP Duplex
YES
YES
YES
HTTP Comet
YES
YES
YES
HTTP
NO
NO
NO
iFrame
NO
NO
NO
Publication
Having decided on your topic structure and the format of your data, consider how you publish
the data through the topics.
Pub-sub is the primary model of data distribution used by Diffusion. Clients subscribe to a topic.
When data is published to the topic as an update, the Diffusion server pushes that update out to
all of the subscribed clients.
Figure 6: Pub-sub model
A client can both publish to topics and subscribe to topics, depending on the permissions that
client has.
Concepts
Update
Diffusion | 64