Resolves #501. Use the full service name in the default mappings for HTTP API, so that multiple services with the same methods can be served (previously /v1/MethodName, now /fully.qualified.ServiceName/MethodName). Adds a check for gRPC requests so that gRPC and HTTP can serve the same paths, since these are the same now — is it reasonable to assume HTTP/2 and application/grpc content types for checking gRPC requests?
Resolves #501. Use the full service name in the default mappings for HTTP API, so that multiple services with the same methods can be served (previously
/v1/MethodName, now/fully.qualified.ServiceName/MethodName). Adds a check for gRPC requests so that gRPC and HTTP can serve the same paths, since these are the same now — is it reasonable to assume HTTP/2 and application/grpc content types for checking gRPC requests?