A suggestion: why not parse the port use c-ares? as the dns srv support
port. Thus will helpful to multiprocess server!
在 2017年2月1日星期三 UTC+8上午2:30:04,Mark D. Roth写道:
>
> I've put together the following gRFC for encoding grpclb data in DNS:
>
> https://github.com/grpc/proposal/pull/10
>
> As per t
I'm sorry, I don't follow your suggestion. What exactly do you mean by
"parse the dns srv support port", and what use-case do you mean by
"multiprocess server"?
On Fri, Aug 11, 2017 at 2:29 AM, 谭锦彪 wrote:
> A suggestion: why not parse the port use c-ares? as the dns srv support
> port. Thus wil
It works fine for me when building from master:
D0811 07:57:48.380480115 16947 simple_request.c:116]
client_peer_before_call=dns://127.0.0.1:1234/foo.com.:23164
D0811 07:57:48.380498101 16947 dns_resolver_ares.c:304]dns_ares_next
is called.
D0811 07:57:48.380896092 16947 grpc_ares_ev_dri
Hi,
The server side gRFC
-
https://github.com/ejona86/proposal/blob/a339b01be9eafffb1adc4db8c782469caed18bdc/A9-server-side-conn-mgt.md
- does not mention that both connection age and connection idle need to be
specified together. So shouldn't the following code use an || instead of &&?
stat
I am seeing issues with how Deadline works at present in the presence of
failing connections. What I found in my tests & research regarding my
Android use case:
- I am missing an option to explicitly fail a connection (signal that
the connection is broken) when a Deadline expires. An exp
Can I call RPCs concurrently from multiple threads on the same stub, or
should each thread have its own stub?
--
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
Multiple threads can share a stub, no problem.
On Fri, Aug 11, 2017 at 7:35 PM wrote:
> Can I call RPCs concurrently from multiple threads on the same stub, or
> should each thread have its own stub?
>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io"