element <direct-protocol> (global)

Namespace:	http://www.mulesoft.org/schema/mule/tcp
Type:	byteOrMessageProtocolType
Content:	empty, 2 attributes
Subst.Gr:	may substitute for element abstract-protocol
Defined:	globally in mule-tcp.xsd; see XML source
Used:	never

Content Model Diagram

XML Representation Summary

<direct-protocol

rethrowExceptionOnRead	=	(xsd:string \| xsd:boolean)
payloadOnly	=	(xsd:string \| xsd:boolean)

May be included in elements by substitutions (4):

connector, connector, connector, polling-connector

Annotation

TCP does not guarantee that data written to a socket is transmitted in a single packet. Using the direct-protocol element to configure the "null" protocol does not change the normal TCP behavior, so message fragmentation may occur. For example, a single sent message may be received in several pieces, each as a separate received message. Typically, it is not a good choice for messaging within Mule, but it may be necessary to interface with external TCP-based protocols.

XML Source (w/o annotations (1); see within schema source)

<xsd:element name="direct-protocol" substitutionGroup="abstract-protocol" type="byteOrMessageProtocolType"/>

XML schema documentation generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.0 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.