Hi Michael,
On Friday, October 27, 2017 at 5:03:33 AM UTC+13, Michael Lumish wrote:
>
> To clarify, are you saying that after your client loses its connection to
> every server, it never reestablishes a connection with any of them?
>
>>
>>
Yes, exactly.
I have a small project and a bash
Yep, I made it more difficult than it needed to be. Disregard :)
On Wednesday, October 25, 2017 at 7:50:29 AM UTC-7, Ryan Lubke wrote:
>
> Hey Folks,
>
> Some background first. We have a requirement to support multiple
> serialization formats. To this end, we've created a backend in Java, and
To clarify, are you saying that after your client loses its connection to
every server, it never reestablishes a connection with any of them?
On Wed, Oct 25, 2017 at 10:42 PM wrote:
> I'm trying to get a gRPC client/server running using nodejs under Docker
> swarm.
>
>
Since Go's API is synchronous/blocking, I am pretty sure that sender always
block until message is actually sent, which will respect HTTP/2 flow
control windows.
If you want an async API, where a sender can queue up messages even before
the receiver can accept them, you could push them into a
Hi all,
We are using self-signed certificates for enabling TLS between servers and
clients. For that we create credentials for C++ server like this
std::shared_ptr GetServerCredentials()
{
grpc::SslServerCredentialsOptions::PemKeyCertPair pkcp;
pkcp.private_key =
Hi all,
Today I made a Go based prototype and proved that it's feasible. Next week
will have a free slot and will try to do it using c++ based library.
Please take a look and give some feedback about the idea and the overall
architecture. As it was a prototype there is no even something