Sends data on a connection.
- iOS 12.0+
- macOS 10.14+
- Mac Catalyst 13.0+
- tvOS 12.0+
- watchOS 5.0+
The data to send on the connection. May be nil if this send marks its context as complete, such as by sending NW_CONNECTION_FINAL_MESSAGE_CONTEXT as the context and marking the send complete to send a write-close.
The context associated with the content, which represents a logical message to be sent on the connection. All content sent within a single context will be sent as an in-order unit, up until the point that the context is marked complete. Once a context is marked complete, it may be re-used as a new logical message. Protocols like TCP that cannot send multiple independent messages at once (serial bytestreams) will only start processing a new context once the prior context has been marked complete. Defaults to NW_CONNECTION_DEFAULT_MESSAGE_CONTEXT.
A flag indicating if the caller's sending context (logical message) is now complete. Until a context is marked complete, content sent for other contexts may not be sent immediately (if the protocol requires sending bytes serially, like TCP). For datagram protocols, like UDP, this flag indicates that the content represents a complete datagram.
When sending using streaming protocols like TCP, this flag can be used to mark the end of a single message on the stream, of which there may be many. However, it can also indicate that the connection should send a "write close" (a TCP FIN) if the sending context is the final context on the connection. Specifically, to send a "write close", pass NW_CONNECTION_FINAL_MESSAGE_CONTEXT or NW_CONNECTION_DEFAULT_STREAM_CONTEXT for the context (or create a custom context and call
nw), and mark the send as complete.
_content _context _set _is _final(_: _:)
A completion handler to notify the caller when content has been processed by the connection, or a marker that this data is idempotent (NW_CONNECTION_SEND_IDEMPOTENT_CONTENT) and may be sent multiple times as fast open data if
_parameters _set _fast _open _enabled(_: _:)