Hi, Thanks for getting back on this. Sure, I'll submit a PR for doc (and code if required). However, I am out for next 3 weeks on a vacation (with limited internet connectivity) so I think the best course of action is to submit the PR after that (just in case it takes a little back and forth). I'll touch base after April 17th.
Thanks. On Tuesday, March 21, 2017 at 3:52:53 PM UTC-7, Craig Tiller wrote: > > The writeup looks great: it'd be good to get this as a .md file in our > doc/c++ tree (would love to see a pull request). > > I know there were some folks looking to update the example code also... > I'm going to have them jump on this thread for where to go with the code. > > On Thursday, March 2, 2017 at 11:34:04 AM UTC-8, Arpit Baldeva wrote: >> >> Hi, >> >> >> >> Recently, I have been looking into the sync and async api of gRPC (C++) >> and how to choose between them for my usage. While gRPC has excellent >> documentation and examples overall, I found this area a bit lacking. So I >> had to go through a lot of past forum posts (and post some myself) for >> gaining insights on the subject. I am attaching a doc here that details the >> difference between the two model. People might find useful when trying to >> make their decision. >> >> >> >> In addition, I implemented a set of classes that makes working with async >> API on server a bit easier from application code point of view. The >> example/test code I found would often ignore the error handling or do >> streaming calls in a way that hardly resembles how you might do things in >> your application. I realize the importance of existing example code as it >> is simple to start with however I feel a more complex example is also >> warranted. Using those utility classes, I went ahead and implemented the >> routeguide server example in a fully async fashion. So I am attaching that >> code as well in the hope that it is something other people can benefit >> from. May be it could become part of example code in gRPC codebase? >> >> >> The code is commented as much as I deemed necessary. I have also stress >> tested it with multiple threads from the client and abrupt client process >> exit. I am also attaching the client stress test code but that bit isn’t >> substantially different from the existing example code around client (apart >> from adding some threading stuff). >> >> >> >> Thanks. >> > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/e06994cc-4099-4a7c-ac38-c5621489cb15%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
