Skip to content

Conversation

@artembilan
Copy link
Member

Fixes #3207

Previously an incoming RSocket Publisher has been decoded as a single unit
leading to extra work on the client side, e.g. a delimiter has to be provided
to treat each payload item as independent

  • To have a consistency with Spring Messaging and its PayloadMethodArgumentResolver
    change an RSocketInboundGateway to process inbound payloads as Flux and decode
    each item independently.
  • Change RSocketDslTests to remove delimiters and make it consistent with the regular
    RSocketRequester client

Copy link
Contributor

@garyrussell garyrussell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs a what's new doc entry.

Doesn't this need an option to revert to previous behavior?

Fixes spring-projects#3207

Previously an incoming RSocket Publisher has been decoded as a single unit
leading to extra work on the client side, e.g. a delimiter has to be provided
to treat each payload item as independent

* To have a consistency with Spring Messaging and its `PayloadMethodArgumentResolver`
change an `RSocketInboundGateway` to process inbound payloads as `Flux` and decode
each item independently.
* Change `RSocketDslTests` to remove delimiters and make it consistent with the regular
`RSocketRequester` client
@garyrussell garyrussell merged commit c45cc66 into spring-projects:master Mar 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rsocket InboundGateway message handling should be consistent with regular @Controller/@MessageMapping

2 participants