Move request start/accept to DuplexConnection?

[rsocket]

Move request start/accept to DuplexConnection?

[tmontgomery]

Couple things.

1. Do we want to continue previous state when re-connecting. This is a fairly big decision because it means Stream IDs can persist across connections. It also means continuations of streams, etc.
2. We could use the spec naming of Connection that has Requester and Responder for each side of the connection. Requester and Responder would replace Client and Server. However, this is all internal. The exposed API should probably only be Connection or similar.

I think it would make sense to hide the protocol processing inside the Connection.

ReactiveSocket.Connection c = createConnection(); // create from some factory
c.requestResponse("some endpoint").subscribe();

[benjchristensen]

Do we want to continue previous state when re-connecting.

We have decided no.

[benjchristensen]

We have changed the design quite a bit since this question. Closing out. Open a new one if current design has issues.