[grpc-io] Re: multiple async clients for route_guide_callback_server example

sorry one correction is, when i mean nothing happens it means client keeps on sending messages but server doesn't receive it and as a result there will be no reply to client On Friday, May 5, 2023 at 10:53:10 PM UTC+5:30 karthik karra wrote: > hi all, below is code which i am trying to make it

[grpc-io] Re: multiple async clients for route_guide_callback_server example

hi all, below is code which i am trying to make it work. after untar copy the files under route_guide folder of examples/cpp in grpc repo. route chat modified code it has cmake file and it will generate client

[grpc-io] Re: multiple async clients for route_guide_callback_server example

anyone was able to get the multiple async client example working. in my example, server is able to receive only single message from each client (i was trying with 2 clients) and both the clients are continuously sending the messages but server is not receiving any thing. Please correct me if

[grpc-io] Re: multiple async clients for route_guide_callback_server example

Could I ask you to create a tracking issue for this on github please? Also if you've got a working solution, contributions to source are welcome :) On Wednesday, March 22, 2023 at 2:52:22 AM UTC-7 Dmitry Gorelov wrote: > Please check the following code, it fixes the crash of the >

[grpc-io] Re: multiple async clients for route_guide_callback_server example

Please check the following code, it fixes the crash of the route_guide_callback_server! #include #include #include #include #include #include #include #include "helper.h" #include

[grpc-io] Re: multiple async clients for route_guide_callback_server example

I found that on a server side the mutex mu is locking only the received_notes. But the to_send_notes are not locked and get accessed from different functions, that are called by bidirectional core from different threads. Slight modification of code made the server stable! (see how I placed

[grpc-io] Re: multiple async clients for route_guide_callback_server example

[image: 2023-03-22 02_14_54-Window.png] среда, 22 марта 2023 г. в 02:00:25 UTC+3, Dmitry Gorelov: > Both of them , the client and server, are from route_guide example. I > left only bidirectional part. > after some attemts to run client, either the client or the server crash. > > Please help

[grpc-io] Re: multiple async clients for route_guide_callback_server example

Both of them , the client and server, are from route_guide example. I left only bidirectional part. after some attemts to run client, either the client or the server crash. Please help to fix them! среда, 22 марта 2023 г. в 01:59:12 UTC+3, Dmitry Gorelov: > //and this is client code > > /*

[grpc-io] Re: multiple async clients for route_guide_callback_server example

//and this is client code /* * * Copyright 2021 gRPC authors. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0

[grpc-io] Re: multiple async clients for route_guide_callback_server example

//this is server code of bidirectional grpc /* * * Copyright 2021 gRPC authors. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * *

[grpc-io] Re: multiple async clients for route_guide_callback_server example

Oh man, it is not working even with *one *client! same problem in proto_utils.h среда, 22 марта 2023 г. в 01:12:55 UTC+3, Dmitry Gorelov: > Hi All, > > please help to modify this peace of server code for bidirectional stream > in order to make it work correclty with *multiple clients* at one

[grpc-io] Re: multiple async clients for route_guide_callback_server example

Oh man... It is not working correclty even with one client... Same problem with segmentation fault. среда, 22 марта 2023 г. в 01:12:55 UTC+3, Dmitry Gorelov: > Hi All, > > please help to modify this peace of server code for bidirectional stream > in order to make it work correclty with