Eric, I think you are right and I misunderstood the original question. Sorry
for that!
Cheers,
Chris.
On 04.05.20 18:19, 'Eric Anderson' via grpc.io wrote:
On Wed, Apr 29, 2020 at 3:21 PM <[email protected]
<mailto:[email protected]>> wrote:
Interesting - thank you very much! I did see this in the StreamObserver doc
<https://grpc.github.io/grpc-java/javadoc/io/grpc/stub/StreamObserver.html>:
"Since individual |StreamObserver|s are not thread-safe, if multiple
threads will be writing
to a |StreamObserver| concurrently, the application must synchronize calls"
That documentation is correct, and gRPC framework abides by it as well. StreamObservers are
not-thread-safe so the caller has to synchronize, if necessary.
It seems like Christoph was describing /calling into/ a StreamObserver. And yes, he is correct, if
you call into a StreamObserver from multiple threads, you must synchronize them yourself. But it
sounded like you were talking /being called/, in which case you don't need to manage synchronization.
--
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] <mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/CA%2B4M1oP6TD79r_0dUEjk1DeqZ-n9SHtQoW0eJwKFPfAwr%2BuMYQ%40mail.gmail.com
<https://groups.google.com/d/msgid/grpc-io/CA%2B4M1oP6TD79r_0dUEjk1DeqZ-n9SHtQoW0eJwKFPfAwr%2BuMYQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/825fde80-c59a-2938-1c42-4eea8ea49b68%40macd.com.
