Abstract service over AsyncRead and AsyncWrite. about tarpc HOT 3 CLOSED

The latest version is now transport agnostic! It's not generic over AsyncRead/AsyncWrite, but it is generic over Stream<Request> + Sink<Response>.

from tarpc.

I don't think abstracting over read/write inherently enables multiplexing services on a single port. Do you agree with that?

from tarpc.

Yeah it does not directly enable that. What I was thinking is that a user needs to provide a multiplexed component so that one TCP connection can be shared as multiple AsyncRead and AsyncWrite, conceptually something like this:

fn multiplex_write_2(x: AsyncWrite) -> (/*W1*/ impl AsyncWrite, /*W2*/ impl AsyncWrite) {/* ... */}
fn multiplex_read_2(x: AsyncRead) -> (/*R1*/ impl AsyncRead, /*R2*/ impl AsyncRead) {/* ... */}

So that writing to W1 should be received by R1 on the other endpoint, and the same for W2 and R2. And use each pair to construct two independent tarpc services.

from tarpc.