Hey guys, We have a desktop application that is designed to integrate with a number of other programs. We have plugins for these programs, and we need them to _discover_ our desktop software. Right now our software is an executable and most plugins are .net assemblies (all plugins are in a GRPC friendly environment) but in the near future I'm hoping to have a windows service/linux daemon, which should mean its always running. But, of course, I need to handle service interruptions. Further, I cannot hard-code to any port because I wont know what ports are available at start time.
Does anybody know of a simple way to negotiate connection strings for grpc clients and servers? I'm thinking about using statically known file paths in combination with registry values and/or environment values to create a kind of queue file, where we can use the file to bootstrap into sockets. What I realize I'm really after is an IPC event bus with gRPC, and what I'd really like to do is make somebody else solve the registration problem. Failing that, can I specify "Files" as a type for the protobuf "Connection" object? That would also let me differ some nasty gotcha's --particularly from Java callers--, and hopefully make for a reasonably elegant grpc document. Any suggestions? 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/634bcd33-cee1-4cc9-8f17-c92d00e1b218%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
