Instance Methodswift-nio 2.72.0NIOCore
write(context:data:promise:)
Codec.swift:722func write(context: ChannelHandlerContext, data: NIOAny, promise: EventLoopPromise<Void>?) func write(context: ChannelHandlerContext, data: NIOAny, promise: EventLoopPromise<Void>?) s7NIOCore20ByteToMessageHandlerCA2A014WriteObservingbcD7DecoderRzrlE5write7context4data7promiseyAA07ChannelE7ContextC_AA6NIOAnyVAA16EventLoopPromiseVyytGSgtFWhat are these?
FNV24: [5H037]
where Decoder:WriteObservingByteToMessageDecoderimport NIOCoreThe core abstractions that make up SwiftNIO.
final class ByteToMessageHandler<Decoder> where Decoder : ByteToMessageDecoderA handler which turns a given ByteToMessageDecoder into a ChannelInboundHandler that can then be added to a ChannelPipeline.
final class ChannelHandlerContextEvery ChannelHandler has – when added to a ChannelPipeline – a corresponding ChannelHandlerContext which is the way ChannelHandlers can interact with other ChannelHandlers in the pipeline.
struct NIOAnyNIOAny is an opaque container for values of any type, similar to Swift’s builtin Any type. Contrary to Any the overhead of NIOAny depends on the the type of the wrapped value. Certain types that are important for the performance of a SwiftNIO application like ByteBuffer, FileRegion and AddressEnvelope<ByteBuffer> can be expected to be wrapped almost without overhead. All others will have similar performance as if they were passed as an Any as NIOAny just like Any will contain them within an existential container.
struct EventLoopPromise<Value>A promise to provide a result later.
typealias Void = ()The return type of functions that don’t explicitly specify a return type, that is, an empty tuple ().
protocol WriteObservingByteToMessageDecoder : ByteToMessageDecoderSome ByteToMessageDecoders need to observe writes (which are outbound events). ByteToMessageDecoders which implement the WriteObservingByteToMessageDecoder protocol will be notified about every outbound write.
typealias OutboundIn = Decoder.OutboundIn