gRPC on Node uses the Node event loop, and it does all of its work on the main thread.
On Fri, Sep 7, 2018 at 11:32 AM Kevin Burton <[email protected]> wrote: > >> Given that information, gRPC does not seem to solve most of those >> problems. You could use it to offload computationally expensive work to >> somewhere else, like with any other client/server setup. >> >>> >>> > I will have to look into the gRPC internals but I assumed that starting it > would yield its own thread and event loop. > > I would probably want to have one thread per IO subsystem though. > > also, this way I can rationalize about IO since I'm just in a single > thread. > > -- > 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/01d70444-44e2-40a5-a49d-c58b30bf671e%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/01d70444-44e2-40a5-a49d-c58b30bf671e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAPK2-4dSkG8isG1Xq4C-UFOGLtOBbTnqp0ve%3D7yEjgbO_MQTaw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
