Most of the docs are on generating a client or server. I would like to take webpieces which has backpressure(by unregistering sockets and re-registering once app code catches up in processing) in both clients and servers. Instead of okhttp client vs. tomcat, it is a unified experience with clients and server sharing http1 and http2 stack. One thing, I am considering is just taking the http2 pieces of webpieces to build a micro-server container. I mean webpieces is good in that it's all a bunch of pieces wired together to make clients or servers. I am now trying to figure out how I could implement on top of gRPC but most documentation is for consumers of existing clients not client authors.
I have used google protobuf in the past, and thrift at twitter. Where can I start to create something that can hopefully leverage existing gRPC parsers and info so I don't have to parse BUT I can then walk the service chain to generate a client and server......hopefully with the gRPC parsers in place(which are hopefully async type parsers that can handle partial parsing!!!). ie. I may have only part of a packet come in from the wire and feed it in and the parser tells me I still need more data much like SSLEngine. Can gRPC be done over http1.1? I may start with the http1.1 client of webpieces if it can. Otherwise, I can use the webpieces http2 client. (the http1 client does not do http2 to keep it lean and vice versa...the http2 client does not do http1 to keep it lean). thanks, Dean -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/63cc249c-bb03-430f-982c-85605dbc4a04%40googlegroups.com.
