Open cangxingzhe opened 2 years ago
Hello, @cangxingzhe you mean for the request to originate from RSocket client, be mapped to HTTP request, sent to HTTP server and then the response mapped back to RSocket?
Trying not to duplicate issues, may I ask if it's being considered the support for the reverse scenario @OlgaMaciaszek:
┌────────┐ HTTP ┌─────────┐ RSOCKET ┌─────────┐
│ ├──────────►│ ├──────────►│ │
│ CLIENT │ │ GATEWAY │ │ SERVICE │
│ │◄──────────┤ │◄──────────┤ │
└────────┘ HTTP └─────────┘ RSOCKET └─────────┘
Or is this the exact purpose of this rsocket-broker-http-bridge
?
@filipeamaral it currently works as you've depicted (thanks for the nice diagram, btw. :)). I guess the issue request is about doing something like this:
┌────────┐ RSOCKET ┌─────────┐ HTTP ┌─────────┐
│ ├──────────►│ ├──────────►│ │
│ RSocket CLIENT │ │ BRIDGE │ │HTTP SERVICE │
│ │◄──────────┤ │◄──────────┤ │
└────────┘ RSOCKET └─────────┘ HTTP └─────────┘
Is this right @cangxingzhe ?
Wow, I am very excited to see this project. I read the source code. There is a doubt: the routing-http-brige currently uses the RSocket client to send requests by resolving urls to route and service. It cannot send request to HTTP server. What's the plan after that?