Skip to content

Deprecate AbstractRSocket and provide alternative #805

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 30, 2020

Conversation

rstoyanchev
Copy link
Contributor

@rstoyanchev rstoyanchev commented Apr 29, 2020

This change deprecates AbstractRSocket in favor of implementing RSocket directly. In turn RSocket has default methods for the basic interactions while onClose() now returns Mono.never() by default and has to be implemented anyway if it is to do something more meaningful.

In addition SocketAcceptor provides static factory methods as shortcuts for handling one type of interaction with a lambda syntax.

@rstoyanchev rstoyanchev added this to the 1.0 milestone Apr 29, 2020
@rstoyanchev rstoyanchev requested a review from OlegDokuka April 29, 2020 15:10
@rstoyanchev rstoyanchev self-assigned this Apr 29, 2020
This change deprecates AbstractRSocket in favor of implementing RSocket
directly. In turn RSocket has default methods for the basic
interactions while onClose now returns Mono.never() by default and has
to be implemented anyway if it is to something more meaningful.

In addition SocketAcceptor provides static factor methods that provide
shortcuts for handling one type of interaction with a lambda syntax.

Signed-off-by: Rossen Stoyanchev <[email protected]>
@OlegDokuka OlegDokuka merged commit d3dc85f into rsocket:develop Apr 30, 2020
@rstoyanchev rstoyanchev deleted the abstract-rsocket branch May 1, 2020 04:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants