Symbols ![]()
loading (3/5)...
Files ![]()
loading (4/5)...
ot::Ip6::Tcp::Endpoint::SendByReference() method
Adds data referenced by the linked buffer pointed to by @p aBuffer to the send buffer. Upon a successful call to this function, the linked buffer and data it references are owned by the TCP stack; they should not be modified by the application until a "send done" callback returns ownership of those objects to the application. It is acceptable to call this function to add another linked buffer to the send queue, even if the "send done" callback for a previous invocation of this function has not yet fired. Note that @p aBuffer should not be chained; its mNext field should be NULL. If additional data will be added right after this call, then the OT_TCP_SEND_MORE_TO_COME flag should be used as a hint to the TCP implementation. @sa otTcpSendByReference
Syntax
Return value
kErrorNone Successfully added data to the send buffer. kErrorFailed Failed to add data to the send buffer.
Related Functions
Found 6 other functions taking a ![]()
otLinkedBuffer
argument:
Function
Description
Provides the application with a linked buffer chain referencing data currently in the TCP receive buffer. The linked buffer chain is valid until the "receive ready" callback is next invoked, or until the next call to otTcpReceiveContiguify() or otTcpCommitReceive().
Provides the application with a linked buffer chain referencing data currently in the TCP receive buffer. The linked buffer chain is valid until the "receive ready" callback is next invoked, or until the next call to otTcpReceiveContiguify() or otTcpCommitReceive(). @sa otTcpReceiveByReference
Adds data referenced by the linked buffer pointed to by @p aBuffer to the send buffer. Upon a successful call to this function, the linked buffer and data it references are owned by the TCP stack; they should not be modified by the application until a "send done" callback returns ownership of those objects to the application. It is acceptable to call this function to add another linked buffer to the send queue, even if the "send done" callback for a previous invocation of this function has not yet fired. Note that @p aBuffer should not be chained; its mNext field should be NULL. If additional data will be added right after this call, then the OT_TCP_SEND_MORE_TO_COME flag should be used as a hint to the TCP implementation.
References
Code
Location