[grpc-io] Re: Why is the server streaming responses in batches instead of one by one?

2016-08-03 Thread Yan Yan
https://github.com/grpc/grpc-go/issues/524#issuecomment-180536815 Go's http2 server does this aggregation automatically. It has a write scheduler that only flushes only when a packet is full or there's nothing else to send. On Thursday, August 4, 2016 at 11:18:00 AM UTC+8, Yan Yan wrote: > >

Re: [grpc-io] client-side retries and idempotency

2016-08-03 Thread 'Josh Humphries' via grpc.io
A custom method option in the proto file is the way we're doing this at Square. We also use other custom method options to influence other kinds of retry policies not implemented in that pull request: latency-triggered retries, where another attempt is made before the first call completes if it's

[grpc-io] client-side retries and idempotency

2016-08-03 Thread Michael Day
Hi everyone, I'm attempting to implement client-side retries using the existing retry interceptors in open pull requests. One of the interceptors (https://github.com/grpc/grpc-java/pull/1570) relies on MethodDescriptor's idempotent field, yet I'm not sure how to set this via my proto

[grpc-io] Re: bazel rules_protobuf (java)

2016-08-03 Thread Paul Grosu
Very cool! If it gets any easier, somehow the image of the people from the movie Wall-E comes to mind :) $ bazel run ProgramCreatorBot On Wednesday, August 3, 2016 at 2:43:42 PM UTC-4, Paul Johnston wrote: > > I've updated rules_protobuf to >

[grpc-io] Re: bazel rules_protobuf (java)

2016-08-03 Thread Paul Johnston
I've updated rules_protobuf to include support for cpp with grpc. This is cool because it uses the grpc BUILD

Re: [grpc-io] accessing authentication context from Python?

2016-08-03 Thread 'Varun Talwar' via grpc.io
+Nathaniel On Wed, Aug 3, 2016 at 4:59 AM, JI Ioannidis wrote: > Consider a simple RPC setup protected with http/2, such as > https://github.com/jayeye/grpc/tree/ji/secure-hello/examples/python/helloworld > > The server will know that the client was properly authenticated,

Re: [grpc-io] Re: Best Practise for Android

2016-08-03 Thread 'Eric Anderson' via grpc.io
On Wed, Aug 3, 2016 at 9:45 AM, wrote: > Thanks for the response, I've added deadlines as a start, so my app is > hanging far less. > In v1.0.0-pre1, we now have some new options that may help prevent/detect hangs. If you're having trouble during periods of activity, you

[grpc-io] Re: Best Practise for Android

2016-08-03 Thread nevilledips
Hi Carl, Thanks for the response, I've added deadlines as a start, so my app is hanging far less. I'll be moving to worker threads and trying out the async API. I'm fairly inexperienced with Java, so the Future API looked like Greek at first read, but I'm sure I'll figure it out. I'm also

Re: [grpc-io] Re: Load balancing gRPC servers

2016-08-03 Thread nevilledips
My bad, I removed my post after I realised that it was by chance. I can confirm that I couldn't get latest nginx to work. I spent the afternoon trying to figure out how to use nghttpx, but I finally got it working 1/2 hour ago. Looks like the 'by chance' part was firewall rules. My Node.js

[grpc-io] Re: Limit max number of connections

2016-08-03 Thread 'Vijay Pai' via grpc.io
There currently isn't such an API from either core or C++ to do so. Depending on the platform, I presume that one could use a process-wide FD limit to limit the number of open connections before starting the server, but that would be outside the current scope of gRPC. Regards, Vijay On