Version: 10.16.0
Namespace

solace.TransportProtocol

Contents

namespace solace.TransportProtocol

Connection scheme types referenced by solace.SessionProperties#transportProtocol, solace.SessionProperties#webTransportProtocolList (browser only), and solace.SessionProperties#transportProtocolInUse.

Static Properties & Enumerations Top

string HTTP_BASE64 = HTTP_BASE64
string HTTP_BINARY = HTTP_BINARY
string HTTP_BINARY_STREAMING = HTTP_BINARY_STREAMING
string WS_BINARY = WS_BINARY

Static Properties & Enumerations Detail Top

static public string HTTP_BASE64 = HTTP_BASE64

A COMET model that uses base64 payload encoding. HTTP responses have a defined Content-Length.

Guaranteed Messaging is incompatbile with HTTP_ transports.

static public string HTTP_BINARY = HTTP_BINARY

A COMET model that uses binary payload encoding. HTTP responses have a defined Content-Length.

Guaranteed Messaging is incompatbile with HTTP_ transports.

static public string HTTP_BINARY_STREAMING = HTTP_BINARY_STREAMING

A COMET model that uses binary payload encoding. HTTP responses use Chunked Transfer-Encoding to stream data from the Solace Message Router to the client without needing to terminate the HTTP response.

Guaranteed Messaging is incompatbile with HTTP_ transports.

static public string WS_BINARY = WS_BINARY

A WebSocket communication channel uses binary payload encoding and provides full-duplex communication between the client and the Solace Message Router over a single TCP connection.

This is the preferred protocol to use if all networking infrastructure betweed the application and the Solace Message router support WebSockets. If this is not the case, it may be necessary to use one of the HTTP protocols that use the COMET model of messaging.

This transport protocol supports Guaranteed Messaging.