You can do this by forking the protoc code generator and adding in the proper path. The path we use is normalized based on experience at Google, but there is nothing strict about it in the protocol. I think all grpc libraries support dynamic method dispatch, so you can us pretty much any formula as long as it follows http.
On Wednesday, November 1, 2017 at 3:01:31 PM UTC-7, Arpit Baldeva wrote: > > Hi, > > Currently, looks like rpc urls are generated in the form of /<package > name>/<rpc name>. Is there a way to prefix the urls such that grpc client > could call <fixed prefix>/<package name>/<rpc name>? The receiver can chop > off the prefix and call the correct rpc. > > Use case: We'd like to have a proxy sitting between our client and grpc > server. The proxy will serve multiple clients. So a client could call > ourdomain.com/<something specific to client>/<package name>/<rpc name>. > The proxy will chop off <something specific to client> and reroute the rpc > to correct handling instance. > > One option to do it would be via custom header but was wondering if url > prefixing has been thought of/brought up before? > > 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/0d58ae2e-9a73-4c2f-b698-ba93da0b7d55%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
