Hello Abhijeet,
There can be a long lived stream that stays alive without the use of a for.
The for (while true essentially) is a convinent way to structure receiving
messages/sending messages. You don't need a for loop/time.Sleep to keep the
stream alive. gRPC-Go server's do fork a goroutine
+grpc-io, so Go folks can answer
On Tue, Mar 19, 2024 at 9:05 PM Abhijeet Tiwari
wrote:
> Hey, thanks a lot for the response!
>
> My server is actually written in golang.
> I also wanted to know that I'll have to use a combination of for loop with
> some time.Sleep() maybe to keep the server
On Wed, Mar 13, 2024 at 1:11 PM Abhijeet Tiwari
wrote:
> 1) let's say a java based client that has opened a server streaming rpc
> 2) after this, we are to receive some info through a webhook on our
> server, but it might take some time
> 3) we have to send this info received over webhook to the
So I was wondering about this usecase:
1) let's say a java based client that has opened a server streaming rpc
2) after this, we are to receive some info through a webhook on our server,
but it might take some time
3) we have to send this info received over webhook to the java based client
over
