Correct encoding and decoding of "message/x.rsocket.routing.v0" #23137
Assignees
Labels
Milestone
Comments
rstoyanchev
added
in: messaging
|
RoutingMetadata implemented on https://github.com/rsocket/rsocket-java/tree/develop/rsocket-core/src/main/java/io/rsocket/metadata |
|
@linux-china, currently we simply take the first tag value. Is this too simplistic perhaps, and is there a more idiomatic way, e.g. one tag with the some name (e.g. "route" or "mapping") + 2nd tag with the actual route value? |
|
Now I think the first tag is ok, and developers can put URI string as tag value, and still flexible. |
artembilan
added a commit
to spring-projects/spring-integration
that referenced
this issue
Sep 3, 2019
Related to spring-projects/spring-framework#23137 The metadata in Spring Messaging for RSockets now supports any arbitrary objects for setup payload, including composition. * Switch the `ClientRSocketConnector` to fully delegate to the `RSocketRequester.Builder` inheriting possible metadata encoding/decoding in the target `RSocketRequester` implementation * Turn off a default `dataMimeType` from the `MimeTypeUtils.TEXT_PLAIN` to the `null` by default relying on the encoder/decoder logic in the target RSocket wrappers * Expose more delegating options in the `ClientRSocketConnector`, like `setupRouteVars`, `setupMetadata`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Composite metadata is now supported as of M3 (see #22798) with the String route added as a
"message/x.rsocket.routing.v0"entry in the composite metadata, plus the option to add more metadata entries. The route is still encoded as a simple String. That needs to be changed when rsocket-core provides an API for that.The text was updated successfully, but these errors were encountered: