So I think grpc could be used to help out with a major issue for Electron apps.
Essentially the main process can be a bottleneck around the UI thread. You basically don't want to lock it up as the IPC can't be used to control the browser process. Additionally, there's the issue of blocking the UI thread with computationally complex activities. On top of that there's an issue of needing a centralized coordinator for some activities like locking, updating files on disk , etc. We could use grpc to solve these problems I think. The grpc daemon could sit outside the main electron and render processes and allow all components to talk to each other and discover each other. It *looks* like grpc-web could solve this but I'm unclear if it works in the renderer process. This would save me a huge amount of time if it were possible to get to work within Electron. Thoughts? -- 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 grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. 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/7ebd434a-d64d-4600-a04f-a1de28dd4407%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
