Ah.. nice.. is that documented anywhere? On Friday, September 7, 2018 at 2:15:32 PM UTC-7, Michael Lumish wrote: > > If you want to use gRPC with electron you have to pass some extra > arguments at installation time to indicate that you want the electron > binaries. So it would look something like this: npm install grpc > --runtime=electron --target=<electron version>. Just replace "<electron > version>" with whatever version of electron you are using. > > On Fri, Sep 7, 2018 at 2:03 PM Kevin Burton <[email protected] > <javascript:>> wrote: > >> I worked on a minimum proof of concept and it looks like grpc requires >> native binaries for electron. >> >> Though I can't seem to find any. Rebuilding for all platforms would be >> very time consuming. >> >> >> On Friday, September 7, 2018 at 2:01:10 PM UTC-7, Kevin Burton wrote: >>> >>> Ah.. ok. that sort of defeats the whole point. There's now way to make >>> it threaded? >>> >>> I was reading in the documentation about ThreadManager and how it uses a >>> thread pool. I was just planning on configuring this for 1 >>> >>> On Friday, September 7, 2018 at 11:35:48 AM UTC-7, Michael Lumish wrote: >>>> >>>> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/dd40cb87-9fcf-48cb-b8b6-028931769948%40googlegroups.com >> >> <https://groups.google.com/d/msgid/grpc-io/dd40cb87-9fcf-48cb-b8b6-028931769948%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/9adbc7b9-164a-4757-b892-9c9972682b22%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
