Class | Description |
---|---|
AbstractByteProtocol |
This Abstract class has been introduced so as to have the byte protocols (i.e.
|
CustomClassLoadingLengthProtocol |
A length protocol that uses a specific class loader to load objects from streams
|
DirectProtocol |
The DirectProtocol class is an application level tcp protocol that does nothing.
|
EOFProtocol |
The EOFProtocol class is an application level tcp protocol that does nothing.
|
LengthProtocol |
The LengthProtocol is an application level tcp protocol that can be used to
transfer large amounts of data without risking some data to be loss.
|
MuleMessageDirectProtocol |
This Protocol will send the actual Mule Message over the TCP channel, and in this
way we are preserving any headers which might be needed, for example Correlation
IDs in order to be able to aggregate messages after chunking.
|
MuleMessageEOFProtocol |
This Protocol will send the actual Mule Message over the TCP channel, and in this
way we are preserving any headers which might be needed, for example Correlation
IDs in order to be able to aggregate messages after chunking.
|
MuleMessageLengthProtocol |
This Protocol will send the actual Mule Message over the TCP channel, and in this
way we are preserving any headers which might be needed, for example Correlation
IDs in order to be able to aggregate messages after chunking.
|
MuleMessageSafeProtocol |
This Protocol will send the actual Mule Message over the TCP channel, and in this
way we are preserving any headers which might be needed, for example Correlation
IDs in order to be able to aggregate messages after chunking.
|
ProtocolStream | |
SafeProtocol |
This precedes every message with a cookie.
|
StreamingProtocol | |
XmlMessageEOFProtocol |
Extend
XmlMessageProtocol to continue reading
until either a new message or EOF is found. |
XmlMessageProtocol |
The XmlMessageProtocol is an application level tcp protocol that can be used to
read streaming xml documents.
|
Copyright © 2003–2016 MuleSoft, Inc.. All rights reserved.