Interface and Description |
---|
io.rsocket.ResponderRSocket
as of 1.0 RC7 in favor of using
RSocket.requestChannel(Publisher) with Flux.switchOnFirst(BiFunction) |
io.rsocket.resume.ResumeStrategy
as of 1.0 RC7 in favor of using
Resume.retry(Retry) via
RSocketConnector or RSocketServer . |
io.rsocket.transport.TransportHeaderAware
as of 1.0.1 in favor using properties on individual transports.
|
Class and Description |
---|
io.rsocket.AbstractRSocket
as of 1.0 in favor of implementing
RSocket directly which has default
methods. |
io.rsocket.metadata.security.AuthMetadataFlyweight
in favor of
AuthMetadataCodec |
io.rsocket.metadata.CompositeMetadataFlyweight
in favor of
CompositeMetadataCodec |
io.rsocket.resume.ExponentialBackoffResumeStrategy
as of 1.0 RC7 in favor of passing
Retry.backoff(long, Duration) to Resume.retry(Retry) . |
io.rsocket.resume.PeriodicResumeStrategy
as of 1.0 RC7 in favor of passing
Retry.fixedDelay(long, Duration) to Resume.retry(Retry) . |
io.rsocket.RSocketFactory
please use
RSocketConnector and RSocketServer . |
io.rsocket.metadata.TaggingMetadataFlyweight
in favor of
TaggingMetadataCodec |
Enum and Description |
---|
io.rsocket.metadata.security.WellKnownAuthType
in favor of
WellKnownAuthType |
Exceptions and Description |
---|
io.rsocket.exceptions.RSocketException
please use
RSocketErrorException instead |
Method and Description |
---|
io.rsocket.RSocketFactory.ClientRSocketFactory.addClientPlugin(RSocketInterceptor) |
io.rsocket.RSocketFactory.ServerRSocketFactory.addClientPlugin(RSocketInterceptor) |
io.rsocket.RSocketFactory.ClientRSocketFactory.addServerPlugin(RSocketInterceptor) |
io.rsocket.RSocketFactory.ServerRSocketFactory.addServerPlugin(RSocketInterceptor) |
io.rsocket.RSocketFactory.ClientRSocketFactory.byteBufAllocator(ByteBufAllocator)
this method is deprecated and deliberately has no effect anymore. Right now, in
order configure the custom
ByteBufAllocator it is recommended to use the
following setup for Reactor Netty based transport: 1. For Client:
2. For server:
Or in case of local transport, to use corresponding factory method LocalClientTransport.creat(String, ByteBufAllocator) |
io.rsocket.RSocketFactory.ServerRSocketFactory.byteBufAllocator(ByteBufAllocator)
this method is deprecated and deliberately has no effect anymore. Right now, in
order configure the custom
ByteBufAllocator it is recommended to use the
following setup for Reactor Netty based transport: 1. For Client:
2. For server:
Or in case of local transport, to use corresponding factory method LocalClientTransport.creat(String, ByteBufAllocator) |
io.rsocket.ConnectionSetupPayload.create(ByteBuf)
as of 1.0 RC7. Please, use
DefaultConnectionSetupPayload constructor. |
io.rsocket.RSocketFactory.ClientRSocketFactory.errorConsumer(Consumer<Throwable>)
this handler is deliberately no-ops and is deprecated with no replacement. In
order to observe errors, it is recommended to add error handler using
doOnError
on the specific logical stream. In order to observe connection, or RSocket terminal
errors, it is recommended to hook on Closeable.onClose() handler. |
io.rsocket.RSocketFactory.ServerRSocketFactory.errorConsumer(Consumer<Throwable>)
this handler is deliberately no-ops and is deprecated with no replacement. In
order to observe errors, it is recommended to add error handler using
doOnError
on the specific logical stream. In order to observe connection, or RSocket terminal
errors, it is recommended to hook on Closeable.onClose() handler. |
io.rsocket.RSocketFactory.ClientRSocketFactory.keepAlive() |
io.rsocket.RSocketFactory.ClientRSocketFactory.singleSubscriberRequester()
without a replacement and no longer used.
|
io.rsocket.RSocketFactory.ServerRSocketFactory.singleSubscriberRequester()
without a replacement and no longer used.
|
Constructor and Description |
---|
io.rsocket.exceptions.SetupException(String) |
io.rsocket.exceptions.SetupException(String, Throwable) |