Interface WriteStream<T>
-
- All Superinterfaces:
StreamBase
- All Known Subinterfaces:
WebSocketBase
- All Known Implementing Classes:
AmqpSender
,AsyncFile
,ClientWebSocket
,GrpcClientRequest
,GrpcServerResponse
,GrpcWriteStream
,HttpClientRequest
,HttpServerResponse
,KafkaProducer
,NetSocket
,ServerWebSocket
,SockJSSocket
,WebSocket
public interface WriteStream<T> extends StreamBase
-
-
Method Summary
All Methods Static Methods Instance Methods Abstract Methods Modifier and Type Method Description WriteStream<T>
drainHandler(Handler<Void> handler)
Set a drain handler on the stream.Completable
end()
Ends the stream.Completable
end(T data)
Same asend()
but writes some data to the stream before ending.WriteStream<T>
exceptionHandler(Handler<Throwable> handler)
Set an exception handler on the write stream.WriteStream
getDelegate()
static <T> WriteStream<T>
newInstance(WriteStream arg)
static <T> WriteStream<T>
newInstance(WriteStream arg, io.vertx.lang.rx.TypeArg<T> __typeArg_T)
Completable
rxEnd()
Ends the stream.Completable
rxEnd(T data)
Same asend()
but writes some data to the stream before ending.Completable
rxWrite(T data)
Write some data to the stream.WriteStream<T>
setWriteQueueMaxSize(int maxSize)
Set the maximum size of the write queue tomaxSize
.WriteStreamObserver<T>
toObserver()
WriteStreamSubscriber<T>
toSubscriber()
Completable
write(T data)
Write some data to the stream.boolean
writeQueueFull()
This will returntrue
if there are more bytes in the write queue than the value set usingsetWriteQueueMaxSize(int)
-
-
-
Method Detail
-
getDelegate
WriteStream getDelegate()
- Specified by:
getDelegate
in interfaceStreamBase
-
exceptionHandler
WriteStream<T> exceptionHandler(Handler<Throwable> handler)
Set an exception handler on the write stream.- Specified by:
exceptionHandler
in interfaceStreamBase
- Parameters:
handler
- the exception handler- Returns:
- a reference to this, so the API can be used fluently
-
write
Completable write(T data)
Write some data to the stream.The data is usually put on an internal write queue, and the write actually happens asynchronously. To avoid running out of memory by putting too much on the write queue, check the
writeQueueFull()
method before writing. This is done automatically if using aPipe
.When the
data
is moved from the queue to the actual medium, the returned will be completed with the write result, e.g the future is succeeded when a server HTTP response buffer is written to the socket and failed if the remote client has closed the socket while the data was still pending for write.- Parameters:
data
- the data to write- Returns:
- a future completed with the write result
-
rxWrite
Completable rxWrite(T data)
Write some data to the stream.The data is usually put on an internal write queue, and the write actually happens asynchronously. To avoid running out of memory by putting too much on the write queue, check the
writeQueueFull()
method before writing. This is done automatically if using aPipe
.When the
data
is moved from the queue to the actual medium, the returned will be completed with the write result, e.g the future is succeeded when a server HTTP response buffer is written to the socket and failed if the remote client has closed the socket while the data was still pending for write.- Parameters:
data
- the data to write- Returns:
- a future completed with the write result
-
end
Completable end()
Ends the stream.Once the stream has ended, it cannot be used any more.
- Returns:
- a future completed with the result
-
rxEnd
Completable rxEnd()
Ends the stream.Once the stream has ended, it cannot be used any more.
- Returns:
- a future completed with the result
-
end
Completable end(T data)
Same asend()
but writes some data to the stream before ending.- Parameters:
data
- the data to write- Returns:
- a future completed with the result
-
rxEnd
Completable rxEnd(T data)
Same asend()
but writes some data to the stream before ending.- Parameters:
data
- the data to write- Returns:
- a future completed with the result
-
setWriteQueueMaxSize
WriteStream<T> setWriteQueueMaxSize(int maxSize)
Set the maximum size of the write queue tomaxSize
. You will still be able to write to the stream even if there is more thanmaxSize
items in the write queue. This is used as an indicator by classes such asPipe
to provide flow control. The value is defined by the implementation of the stream, e.g in bytes for aNetSocket
, etc...- Parameters:
maxSize
- the max size of the write stream- Returns:
- a reference to this, so the API can be used fluently
-
writeQueueFull
boolean writeQueueFull()
This will returntrue
if there are more bytes in the write queue than the value set usingsetWriteQueueMaxSize(int)
- Returns:
true
if write queue is full
-
drainHandler
WriteStream<T> drainHandler(Handler<Void> handler)
Set a drain handler on the stream. If the write queue is full, then the handler will be called when the write queue is ready to accept buffers again. SeePipe
for an example of this being used.The stream implementation defines when the drain handler, for example it could be when the queue size has been reduced to
maxSize / 2
.- Parameters:
handler
- the handler- Returns:
- a reference to this, so the API can be used fluently
-
toObserver
WriteStreamObserver<T> toObserver()
-
toSubscriber
WriteStreamSubscriber<T> toSubscriber()
-
newInstance
static <T> WriteStream<T> newInstance(WriteStream arg)
-
newInstance
static <T> WriteStream<T> newInstance(WriteStream arg, io.vertx.lang.rx.TypeArg<T> __typeArg_T)
-
-