Skip to content

Restore ConnectionSetupPayload as abstract class#785

Merged
OlegDokuka merged 1 commit into
rsocket:developfrom
rstoyanchev:778-setup
Apr 18, 2020
Merged

Restore ConnectionSetupPayload as abstract class#785
OlegDokuka merged 1 commit into
rsocket:developfrom
rstoyanchev:778-setup

Conversation

@rstoyanchev

Copy link
Copy Markdown
Contributor

Follow-up fix for 0ac54d4.

Changing ConnectionSetupPayload from abstract class to interface is problematic when framework code compiled against newer RSocket is used in an application on existing version. It is now restored as an abstract class. DefaultConnectionSetupPayload however remains in the "core" sub-package to avoid the package cycle with "frame".

Another follow-up fix for commit 0ac54d4. Changing ConnectionSetupPayload
from abstract class to interface is problematic when framework code
compiled against newer RSocket is used in an application on existing
version.

ConnectionSetupPayload is now an abstract class again but
DefaultConnectionSetupPayload remains in the "core" sub-package to avoid
the package cycle with "frame".

See rsocketgh-778

Signed-off-by: Rossen Stoyanchev <rstoyanchev@pivotal.io>
@OlegDokuka
OlegDokuka merged commit cf3bf11 into rsocket:develop Apr 18, 2020
@rstoyanchev
rstoyanchev deleted the 778-setup branch April 18, 2020 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants