On Fri, Oct 7, 2016 at 4:05 PM, Malc <markitm...@gmail.com> wrote:
> I have a slightly different usecase in mind.
> We would like to move a legacy system to using gRPC. All new stuff can go
> there easy; but for the older components it would be useful to migrate
> first to an in-process separation of interface, and then to pull those out
> into external services as we get more mature in them.
> Being in the same memory space allows us to start building an interface
> while having some of the more malignant elements still worming their way
> through the global namespace; until we pick those out too.
> Is there a likely date in the future that this might be available?
At this point, there's no ETA, and it's very unlikely this would happen
before the end of 2016. On the other hand, for what you are describing, you
don't really need an in-process server. You can run a server on localhost
(on an autoselected port) and then connect to it with your clients. You can
have as many servers and clients in the same process as you want. Memory
space will be the same you cheating as you describe it will be possible.
> 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 firstname.lastname@example.org.
> Visit this group at https://groups.google.com/group/grpc-io.
> To view this discussion on the web visit https://groups.google.com/d/
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.