Re: [grpc-io] python gRPC: set max_message_length for server or listen port.

Thanks. We will wait for 1.1 release :) понедельник, 23 января 2017 г., 21:18:12 UTC+2 пользователь Ken Payson написал: > > Currently this is not possible in Python. > > In the master branch > , > > there is an

[grpc-io] Re: [grpc-java] using NameResolver for grpc servers with TLS

On Thursday, January 26, 2017 at 8:52:54 PM UTC+1, Carl Mastrangelo wrote: > > Name resolution happens before the connection, so I'm not sure what you > mean by "connection in progress". Could you clarify? > Well since the authority() returned by the NameResolver is used during setup of the

[grpc-io] Re: Using gRPC as a IoT protocol instead of LWM2M/CoAP

Although there has been some gRPC IoT work, I don't think that any team members have expertise in the technologies that you've described. Maybe you can get an answer on this forum from a community member, or perhaps on another forum like StackOverflow? Best regards, Vijay On Sunday, January 22,

Re: [grpc-io] Re: gRFC A1: HTTP CONNECT proxy support

On Thu, Jan 26, 2017 at 11:58 AM, Eric Anderson wrote: > On Thu, Jan 26, 2017 at 8:42 AM, 'Mark D. Roth' via grpc.io < > grpc-io@googlegroups.com> wrote: >> >>- *All* requests must go through the proxy, both for internal and >> external servers. > > > This is not true. It only

Re: [grpc-io] gRFC A2: Service Configs in DNS

On Thu, Jan 26, 2017 at 12:52 PM, 'Mark D. Roth' via grpc.io < grpc-io@googlegroups.com> wrote: > We might be able to ameliorate some of that by allowing some sort of > simple pattern-matching language, although I'd prefer to avoid taking an > external dependency on a regexp library, so it would p

Re: [grpc-io] Re: gRFC A1: HTTP CONNECT proxy support

On Wed, Jan 25, 2017 at 5:40 PM, Julien Boeuf wrote: > I think "when it sees the proxy address" also has fundamental issues, like >> requiring the proxy to have a hard-coded stable IP. That means you couldn't >> add a new proxy to the rotation if experiencing too much load. >> >> More likely, in

[grpc-io] Re: [grpc-java] using NameResolver for grpc servers with TLS

FYI: I got a similar error.. https://github.com/grpc/grpc-java/pull/2662 explains our configuration. On Thursday, January 26, 2017 at 11:52:54 AM UTC-8, Carl Mastrangelo wrote: > > Name resolution happens before the connection, so I'm not sure what you > mean by "connection in progress". Could

Re: [grpc-io] Re: gRFC A1: HTTP CONNECT proxy support

On Thu, Jan 26, 2017 at 8:42 AM, 'Mark D. Roth' via grpc.io < grpc-io@googlegroups.com> wrote: > >- *All* requests must go through the proxy, both for internal and > external servers. This is not true. It only applies to external servers. It directly contradicts the earl

[grpc-io] Re: [grpc-java] using NameResolver for grpc servers with TLS

Name resolution happens before the connection, so I'm not sure what you mean by "connection in progress". Could you clarify? Also, ClientInterceptors work on an RPC level, not a connection level. You can change the authority there, but thats mainly for reducing connections that go through t

Re: [grpc-io] gRFC A2: Service Configs in DNS

On Wed, Jan 25, 2017 at 6:39 PM, Rudi Chiarito wrote: > On Tue, Jan 24, 2017 at 1:37 PM, Mark D. Roth wrote: >> >> I started a similar discussion on canarying ConfigMaps under Kubernetes. >>> While this design is the way at least one push mechanism inside Google >>> works, there's also a more pr

[grpc-io] Re: gRPC multiple services in cpp async server

I would suggest, based on your description, that you might just want multiple methods in the same service (which you can do by just declaring multiple different rpc entries in your .proto file). If you need multiple services, though, you can do that just by registering each service one after an

Re: [grpc-io] about Read/Write on ServerAsyncReaderWriter

Hi, >> My question is that before the cq (write) event is notified, does it allow to write another message? I As you correctly noticed, a second write is not allowed until you do a cq->next() and make sure that the first write is done (the tag for the first write operation is returned from the co

Re: [grpc-io] Re: gRFC A1: HTTP CONNECT proxy support

Replies inline. Please let me know if you want to chat about any of this in person. On Wed, Jan 25, 2017 at 4:13 PM, 'Eric Anderson' via grpc.io < grpc-io@googlegroups.com> wrote: > On Wed, Jan 25, 2017 at 2:00 PM, Mark D. Roth wrote: > >> On Wed, Jan 25, 2017 at 12:59 PM, 'Eric Anderson' via g

[grpc-io] Re: [grpc-java] using NameResolver for grpc servers with TLS

Hi, The error is caused by my NameResolver implementation returning the service id as authority: public class DiscoveryClientNameResolver extends NameResolver { private DiscoveryClient discoveryClient; private final String name; private Listener listener; public DiscoveryClientNameReso

[grpc-io] Re: [grpc-java] using NameResolver for grpc servers with TLS

Small mistake in my mail, the stacktrace is shown clientside NOT serverside. Jorg On Thursday, January 26, 2017 at 1:13:07 PM UTC+1, Jorg Heymans wrote: > > Hi, > > I have a grpc client-server setup using TLS (ClientAuth.REQUIRE) which is > working fine. I am now trying to implement service di

[grpc-io] [grpc-java] using NameResolver for grpc servers with TLS

Hi, I have a grpc client-server setup using TLS (ClientAuth.REQUIRE) which is working fine. I am now trying to implement service discovery using Spring DiscoveryClient and zookeeper, very much like what was done here for eureka https://gist.github.com/Xorlev/eafce32667931b78fac003f228cedc53#fil