Is there a writeup on how to introduce a new transport layer?

[farid.m...@gmail.com]

Title says it all.
I'd like to write a new transport layer and wondering if someone has a good writeup on how to do it.

[Carl Mastrangelo]

No, there is not.  There are very few transports so far, so there hasn't really been much time (or demand) for new transports to be created.  

What transport did you have in mind? 

[Sergey Shalnov]

Hi,

I have no answer to the question but I would recommend to look for this potic https://groups.google.com/d/topic/grpc-io/6-DyXDp2WiY/discussion

Sergey

[Eric Anderson]

In addition to transport, what language do you want to do it in?

On Thu, Aug 4, 2016 at 10:14 AM, <farid.m...@gmail.com> wrote:

Title says it all.
I'd like to write a new transport layer and wondering if someone has a good writeup on how to do it.

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/5a09be5b-29f5-4a82-b0d5-02e346facbd5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Farid Zakaria]

I was looking to do it in Java.

I got pretty far from just following the OkHttp and Netty one but it only gets clearer what pieces I'm missing as I begin to wire in the ServerBuilder and friends.

Farid Zakaria

[Eric Anderson]

InProcess is the smallest transport by far (~500 lines for all the meat of client+server), but it does a poor job of helping you understand the threading model and how to use AbstractStream2[1] and friends.

AbstractStream2 is much easier to figure out how to use (vs AbstractStream), but it is still a bit dense. Are you doing both client and server?

1. FYI, https://github.com/grpc/grpc-java/pull/2140