Class NetSocket
- java.lang.Object
-
- io.vertx.reactivex.core.net.NetSocket
-
- All Implemented Interfaces:
ReadStream<Buffer>
,StreamBase
,WriteStream<Buffer>
public class NetSocket extends Object implements ReadStream<Buffer>, WriteStream<Buffer>
Represents a socket-like interface to a TCP connection on either the client or the server side.Instances of this class are created on the client side by an
NetClient
when a connection to a server is made, or on the server side by aNetServer
when a server accepts a connection.It implements both and so it can be used with
NOTE: This class has been automatically generated from thePipe
to pipe data with flow control.original
non RX-ified interface using Vert.x codegen.
-
-
Field Summary
Fields Modifier and Type Field Description static TypeArg<NetSocket>
__TYPE_ARG
-
Method Summary
All Methods Static Methods Instance Methods Concrete Methods Modifier and Type Method Description String
applicationLayerProtocol()
void
close()
Close the NetSocket and notify thehandler
when the operation completes.void
close(Handler<AsyncResult<Void>> handler)
Close the NetSocket and notify thehandler
when the operation completes.NetSocket
closeHandler(Handler<Void> handler)
Set a handler that will be called when the NetSocket is closedNetSocket
drainHandler(Handler<Void> handler)
Set a drain handler on the stream.void
end()
void
end(Handler<AsyncResult<Void>> handler)
void
end(Buffer data)
Same as but with anhandler
called when the operation completesvoid
end(Buffer data, Handler<AsyncResult<Void>> handler)
Same as but with anhandler
called when the operation completesNetSocket
endHandler(Handler<Void> endHandler)
This handler might be called after the close handler when the socket is paused and there are still buffers to deliver.boolean
equals(Object o)
NetSocket
exceptionHandler(Handler<Throwable> handler)
Set an exception handler on the read stream.NetSocket
fetch(long amount)
Fetch the specifiedamount
of elements.NetSocket
getDelegate()
NetSocket
handler(Handler<Buffer> handler)
Set a data handler.int
hashCode()
String
indicatedServerName()
Returns the SNI server name presented during the SSL handshake by the client.boolean
isSsl()
SocketAddress
localAddress()
SocketAddress
localAddress(boolean real)
static NetSocket
newInstance(NetSocket arg)
NetSocket
pause()
Pause theReadStream
, it sets the buffer infetch
mode and clears the actual demand.Pipe<Buffer>
pipe()
Pause this stream and return a to transfer the elements of this stream to a destination .void
pipeTo(WriteStream<Buffer> dst)
Pipe thisReadStream
to theWriteStream
.void
pipeTo(WriteStream<Buffer> dst, Handler<AsyncResult<Void>> handler)
Pipe thisReadStream
to theWriteStream
.SocketAddress
remoteAddress()
SocketAddress
remoteAddress(boolean real)
NetSocket
resume()
Resume reading, and sets the buffer inflowing
mode.io.reactivex.Completable
rxClose()
Close the NetSocket and notify thehandler
when the operation completes.io.reactivex.Completable
rxEnd()
io.reactivex.Completable
rxEnd(Buffer data)
Same as but with anhandler
called when the operation completesio.reactivex.Completable
rxPipeTo(WriteStream<Buffer> dst)
Pipe thisReadStream
to theWriteStream
.io.reactivex.Completable
rxSendFile(String filename)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurredio.reactivex.Completable
rxSendFile(String filename, long offset)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurredio.reactivex.Completable
rxSendFile(String filename, long offset, long length)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurredio.reactivex.Completable
rxUpgradeToSsl()
Upgrade channel to use SSL/TLS.io.reactivex.Completable
rxUpgradeToSsl(String serverName)
Upgrade channel to use SSL/TLS.io.reactivex.Completable
rxWrite(Buffer message)
LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the message has been written or failed to be written.io.reactivex.Completable
rxWrite(String str)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completesio.reactivex.Completable
rxWrite(String str, String enc)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completesNetSocket
sendFile(String filename)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurredNetSocket
sendFile(String filename, long offset)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurredNetSocket
sendFile(String filename, long offset, long length)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurredNetSocket
sendFile(String filename, long offset, long length, Handler<AsyncResult<Void>> resultHandler)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurredNetSocket
sendFile(String filename, long offset, Handler<AsyncResult<Void>> resultHandler)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurredNetSocket
sendFile(String filename, Handler<AsyncResult<Void>> resultHandler)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurredNetSocket
setWriteQueueMaxSize(int maxSize)
Set the maximum size of the write queue tomaxSize
.SSLSession
sslSession()
io.reactivex.Flowable<Buffer>
toFlowable()
io.reactivex.Observable<Buffer>
toObservable()
WriteStreamObserver<Buffer>
toObserver()
String
toString()
WriteStreamSubscriber<Buffer>
toSubscriber()
NetSocket
upgradeToSsl()
Upgrade channel to use SSL/TLS.NetSocket
upgradeToSsl(Handler<AsyncResult<Void>> handler)
Upgrade channel to use SSL/TLS.NetSocket
upgradeToSsl(String serverName)
Upgrade channel to use SSL/TLS.NetSocket
upgradeToSsl(String serverName, Handler<AsyncResult<Void>> handler)
Upgrade channel to use SSL/TLS.void
write(Buffer message)
LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the message has been written or failed to be written.void
write(Buffer message, Handler<AsyncResult<Void>> handler)
LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the message has been written or failed to be written.void
write(String str)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completesvoid
write(String str, Handler<AsyncResult<Void>> handler)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completesvoid
write(String str, String enc)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completesvoid
write(String str, String enc, Handler<AsyncResult<Void>> handler)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completesString
writeHandlerID()
When aNetSocket
is created, it may register an event handler with the event bus, the ID of that handler is given bywriteHandlerID
.boolean
writeQueueFull()
This will returntrue
if there are more bytes in the write queue than the value set usingsetWriteQueueMaxSize(int)
-
-
-
Method Detail
-
getDelegate
public NetSocket getDelegate()
- Specified by:
getDelegate
in interfaceReadStream<Buffer>
- Specified by:
getDelegate
in interfaceStreamBase
- Specified by:
getDelegate
in interfaceWriteStream<Buffer>
-
toObservable
public io.reactivex.Observable<Buffer> toObservable()
- Specified by:
toObservable
in interfaceReadStream<Buffer>
-
toFlowable
public io.reactivex.Flowable<Buffer> toFlowable()
- Specified by:
toFlowable
in interfaceReadStream<Buffer>
-
toObserver
public WriteStreamObserver<Buffer> toObserver()
-
toSubscriber
public WriteStreamSubscriber<Buffer> toSubscriber()
-
pipe
public Pipe<Buffer> pipe()
Pause this stream and return a to transfer the elements of this stream to a destination . The stream will be resumed when the pipe will be wired to aWriteStream
.- Specified by:
pipe
in interfaceReadStream<Buffer>
- Returns:
- a pipe
-
pipeTo
public void pipeTo(WriteStream<Buffer> dst, Handler<AsyncResult<Void>> handler)
Pipe thisReadStream
to theWriteStream
.Elements emitted by this stream will be written to the write stream until this stream ends or fails.
Once this stream has ended or failed, the write stream will be ended and the
handler
will be called with the result.- Specified by:
pipeTo
in interfaceReadStream<Buffer>
- Parameters:
dst
- the destination write streamhandler
-
-
pipeTo
public void pipeTo(WriteStream<Buffer> dst)
Pipe thisReadStream
to theWriteStream
.Elements emitted by this stream will be written to the write stream until this stream ends or fails.
Once this stream has ended or failed, the write stream will be ended and the
handler
will be called with the result.- Specified by:
pipeTo
in interfaceReadStream<Buffer>
- Parameters:
dst
- the destination write stream
-
rxPipeTo
public io.reactivex.Completable rxPipeTo(WriteStream<Buffer> dst)
Pipe thisReadStream
to theWriteStream
.Elements emitted by this stream will be written to the write stream until this stream ends or fails.
Once this stream has ended or failed, the write stream will be ended and the
handler
will be called with the result.- Specified by:
rxPipeTo
in interfaceReadStream<Buffer>
- Parameters:
dst
- the destination write stream- Returns:
-
end
public void end(Buffer data, Handler<AsyncResult<Void>> handler)
Same as but with anhandler
called when the operation completes- Specified by:
end
in interfaceWriteStream<Buffer>
- Parameters:
data
-handler
-
-
end
public void end(Buffer data)
Same as but with anhandler
called when the operation completes- Specified by:
end
in interfaceWriteStream<Buffer>
- Parameters:
data
-
-
rxEnd
public io.reactivex.Completable rxEnd(Buffer data)
Same as but with anhandler
called when the operation completes- Specified by:
rxEnd
in interfaceWriteStream<Buffer>
- Parameters:
data
-- Returns:
-
writeQueueFull
public boolean writeQueueFull()
This will returntrue
if there are more bytes in the write queue than the value set usingsetWriteQueueMaxSize(int)
- Specified by:
writeQueueFull
in interfaceWriteStream<Buffer>
- Returns:
true
if write queue is full
-
exceptionHandler
public NetSocket exceptionHandler(Handler<Throwable> handler)
Description copied from interface:ReadStream
Set an exception handler on the read stream.- Specified by:
exceptionHandler
in interfaceReadStream<Buffer>
- Specified by:
exceptionHandler
in interfaceStreamBase
- Specified by:
exceptionHandler
in interfaceWriteStream<Buffer>
- Parameters:
handler
- the exception handler- Returns:
- a reference to this, so the API can be used fluently
-
handler
public NetSocket handler(Handler<Buffer> handler)
Description copied from interface:ReadStream
Set a data handler. As data is read, the handler will be called with the data.- Specified by:
handler
in interfaceReadStream<Buffer>
- Returns:
- a reference to this, so the API can be used fluently
-
pause
public NetSocket pause()
Description copied from interface:ReadStream
Pause theReadStream
, it sets the buffer infetch
mode and clears the actual demand.While it's paused, no data will be sent to the data
handler
.- Specified by:
pause
in interfaceReadStream<Buffer>
- Returns:
- a reference to this, so the API can be used fluently
-
resume
public NetSocket resume()
Description copied from interface:ReadStream
Resume reading, and sets the buffer inflowing
mode. If theReadStream
has been paused, reading will recommence on it.- Specified by:
resume
in interfaceReadStream<Buffer>
- Returns:
- a reference to this, so the API can be used fluently
-
fetch
public NetSocket fetch(long amount)
Description copied from interface:ReadStream
Fetch the specifiedamount
of elements. If theReadStream
has been paused, reading will recommence with the specifiedamount
of items, otherwise the specifiedamount
will be added to the current stream demand.- Specified by:
fetch
in interfaceReadStream<Buffer>
- Returns:
- a reference to this, so the API can be used fluently
-
endHandler
public NetSocket endHandler(Handler<Void> endHandler)
This handler might be called after the close handler when the socket is paused and there are still buffers to deliver.
- Specified by:
endHandler
in interfaceReadStream<Buffer>
- Parameters:
endHandler
-- Returns:
-
setWriteQueueMaxSize
public NetSocket setWriteQueueMaxSize(int maxSize)
Description copied from interface:WriteStream
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...- Specified by:
setWriteQueueMaxSize
in interfaceWriteStream<Buffer>
- Parameters:
maxSize
- the max size of the write stream- Returns:
- a reference to this, so the API can be used fluently
-
drainHandler
public NetSocket drainHandler(Handler<Void> handler)
Description copied from interface:WriteStream
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
.- Specified by:
drainHandler
in interfaceWriteStream<Buffer>
- Parameters:
handler
- the handler- Returns:
- a reference to this, so the API can be used fluently
-
writeHandlerID
public String writeHandlerID()
When aNetSocket
is created, it may register an event handler with the event bus, the ID of that handler is given bywriteHandlerID
.By default, no handler is registered, the feature must be enabled via
NetClientOptions
orNetServerOptions
.Given this ID, a different event loop can send a buffer to that event handler using the event bus and that buffer will be received by this instance in its own event loop and written to the underlying connection. This allows you to write data to other connections which are owned by different event loops.
- Returns:
- the write handler ID
-
write
public void write(String str, Handler<AsyncResult<Void>> handler)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completes- Parameters:
str
-handler
-
-
write
public void write(String str)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completes- Parameters:
str
-
-
rxWrite
public io.reactivex.Completable rxWrite(String str)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completes- Parameters:
str
-- Returns:
-
write
public void write(String str, String enc, Handler<AsyncResult<Void>> handler)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completes- Parameters:
str
-enc
-handler
-
-
write
public void write(String str, String enc)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completes- Parameters:
str
-enc
-
-
rxWrite
public io.reactivex.Completable rxWrite(String str, String enc)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the operation completes- Parameters:
str
-enc
-- Returns:
-
write
public void write(Buffer message, Handler<AsyncResult<Void>> handler)
LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the message has been written or failed to be written.- Specified by:
write
in interfaceWriteStream<Buffer>
- Parameters:
message
-handler
-
-
write
public void write(Buffer message)
LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the message has been written or failed to be written.- Specified by:
write
in interfaceWriteStream<Buffer>
- Parameters:
message
-
-
rxWrite
public io.reactivex.Completable rxWrite(Buffer message)
LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but with anhandler
called when the message has been written or failed to be written.- Specified by:
rxWrite
in interfaceWriteStream<Buffer>
- Parameters:
message
-- Returns:
-
sendFile
public NetSocket sendFile(String filename, Handler<AsyncResult<Void>> resultHandler)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename
- file name of the file to sendresultHandler
- handler- Returns:
- a reference to this, so the API can be used fluently
-
sendFile
public NetSocket sendFile(String filename)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename
- file name of the file to send- Returns:
- a reference to this, so the API can be used fluently
-
rxSendFile
public io.reactivex.Completable rxSendFile(String filename)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename
- file name of the file to send- Returns:
- a reference to this, so the API can be used fluently
-
sendFile
public NetSocket sendFile(String filename, long offset, Handler<AsyncResult<Void>> resultHandler)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename
- file name of the file to sendoffset
- offsetresultHandler
- handler- Returns:
- a reference to this, so the API can be used fluently
-
sendFile
public NetSocket sendFile(String filename, long offset)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename
- file name of the file to sendoffset
- offset- Returns:
- a reference to this, so the API can be used fluently
-
rxSendFile
public io.reactivex.Completable rxSendFile(String filename, long offset)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename
- file name of the file to sendoffset
- offset- Returns:
- a reference to this, so the API can be used fluently
-
sendFile
public NetSocket sendFile(String filename, long offset, long length, Handler<AsyncResult<Void>> resultHandler)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename
- file name of the file to sendoffset
- offsetlength
- lengthresultHandler
- handler- Returns:
- a reference to this, so the API can be used fluently
-
sendFile
public NetSocket sendFile(String filename, long offset, long length)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename
- file name of the file to sendoffset
- offsetlength
- length- Returns:
- a reference to this, so the API can be used fluently
-
rxSendFile
public io.reactivex.Completable rxSendFile(String filename, long offset, long length)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)
but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename
- file name of the file to sendoffset
- offsetlength
- length- Returns:
- a reference to this, so the API can be used fluently
-
remoteAddress
public SocketAddress remoteAddress()
- Returns:
- the remote address for this connection, possibly
null
(e.g a server bound on a domain socket). IfuseProxyProtocol
is set totrue
, the address returned will be of the actual connecting client.
-
remoteAddress
public SocketAddress remoteAddress(boolean real)
- Parameters:
real
-- Returns:
-
localAddress
public SocketAddress localAddress()
- Returns:
- the local address for this connection, possibly
null
(e.g a server bound on a domain socket) IfuseProxyProtocol
is set totrue
, the address returned will be of the proxy.
-
localAddress
public SocketAddress localAddress(boolean real)
- Parameters:
real
-- Returns:
-
end
public void end(Handler<AsyncResult<Void>> handler)
- Specified by:
end
in interfaceWriteStream<Buffer>
- Parameters:
handler
-
-
end
public void end()
- Specified by:
end
in interfaceWriteStream<Buffer>
-
rxEnd
public io.reactivex.Completable rxEnd()
- Specified by:
rxEnd
in interfaceWriteStream<Buffer>
- Returns:
-
close
public void close(Handler<AsyncResult<Void>> handler)
Close the NetSocket and notify thehandler
when the operation completes.- Parameters:
handler
-
-
close
public void close()
Close the NetSocket and notify thehandler
when the operation completes.
-
rxClose
public io.reactivex.Completable rxClose()
Close the NetSocket and notify thehandler
when the operation completes.- Returns:
-
closeHandler
public NetSocket closeHandler(Handler<Void> handler)
Set a handler that will be called when the NetSocket is closed- Parameters:
handler
- the handler- Returns:
- a reference to this, so the API can be used fluently
-
upgradeToSsl
public NetSocket upgradeToSsl(Handler<AsyncResult<Void>> handler)
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Parameters:
handler
- the handler will be notified when it's upgraded- Returns:
- a reference to this, so the API can be used fluently
-
upgradeToSsl
public NetSocket upgradeToSsl()
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Returns:
- a reference to this, so the API can be used fluently
-
rxUpgradeToSsl
public io.reactivex.Completable rxUpgradeToSsl()
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Returns:
- a reference to this, so the API can be used fluently
-
upgradeToSsl
public NetSocket upgradeToSsl(String serverName, Handler<AsyncResult<Void>> handler)
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Parameters:
serverName
- the server namehandler
- the handler will be notified when it's upgraded- Returns:
- a reference to this, so the API can be used fluently
-
upgradeToSsl
public NetSocket upgradeToSsl(String serverName)
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Parameters:
serverName
- the server name- Returns:
- a reference to this, so the API can be used fluently
-
rxUpgradeToSsl
public io.reactivex.Completable rxUpgradeToSsl(String serverName)
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Parameters:
serverName
- the server name- Returns:
- a reference to this, so the API can be used fluently
-
isSsl
public boolean isSsl()
- Returns:
- true if this
NetSocket
is encrypted via SSL/TLS.
-
indicatedServerName
public String indicatedServerName()
Returns the SNI server name presented during the SSL handshake by the client.- Returns:
- the indicated server name
-
applicationLayerProtocol
public String applicationLayerProtocol()
- Returns:
- the application-level protocol negotiated during the TLS handshake
-
sslSession
public SSLSession sslSession()
- Returns:
- SSLSession associated with the underlying socket. Returns null if connection is not SSL.
-
-