gRPC static paths?

[song...@hotmail.com]

Hi

I am reading gRPC FAQ "Why is gRPC better/worse than REST?" The answer says "We diverge from typical REST conventions as we use static paths for performance reasons during call dispatch as parsing call parameters from paths, query parameters and payload body adds latency and complexity." What does "static paths" mean here? I think it should not be network routing paths because it does not make sense at all. Can someone please explain a bit what the static paths mean here? Thanks in advance!

[Louis Ryan]

Its the difference between "/service/method" (a fixed string identifying the operation - RPC) and /collection/{resource-id} (where a parameter of the call is a variable component of the REST path). Using fixed strings speeds up dispatching logic and on HTTP2 improves header caching behaviors.

On Wed, Oct 19, 2016 at 1:55 PM, <song...@hotmail.com> wrote:

Hi

I am reading gRPC FAQ "Why is gRPC better/worse than REST?" The answer says "We diverge from typical REST conventions as we use static paths for performance reasons during call dispatch as parsing call parameters from paths, query parameters and payload body adds latency and complexity." What does "static paths" mean here? I think it should not be network routing paths because it does not make sense at all. Can someone please explain a bit what the static paths mean here? Thanks in advance!

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@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/d693df45-01c6-4e03-8c84-b479c9cef24a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.