1xX69
1xX69
The messages can also have super-duper-long names, for example [`VideoActionRecognitionPredictionInstance`](https://github.com/googleapis/googleapis/blob/master/google/cloud/aiplatform/v1/schema/predict/instance/video_action_recognition.proto#L28-L50) (this one is used _indirectly_ though, under [`PredictRequest`](https://github.com/googleapis/googleapis/blob/3acfdb6166a7101691cdf812bf8f8a67a2084fde/google/ai/generativelanguage/v1alpha/prediction_service.proto#L44-L62))
That's the longest method name I've found -- [`UpdateSecurityHealthAnalyticsCustomModule`](https://github.com/googleapis/googleapis/blob/3acfdb6166a7101691cdf812bf8f8a67a2084fde/google/cloud/securitycenter/v1/securitycenter_service.proto#L717-L739)
> I do not like the fact that they aren't following something obvious: https://github.com/googleapis/googleapis/blob/3acfdb6166a7101691cdf812bf8f8a67a2084fde/google/ads/searchads360/v0/services/search_ads360_service.proto#L111-L129 > > Like `[service name][rpc name][Request|Response]` that is a very confusing name Seems relevant: https://github.com/aip-dev/google.aip.dev/issues/1085
I propose to standardize the following terminology: From https://github.com/aip-dev/google.aip.dev/blob/d7c7bdb37ef84c0bce8250a5129b134617b5dfcd/aip/general/0009.md?plain=1#L50: > ### API Interface > The element of an API specification IDL that groups API methods, such as a Protocol Buffers...
> "Physically", you may want one port behind 1 service, but logically, that service has many resources ... so, you end up with such long naming. You _may_ host multiple...
What exactly are you comparing? I'm not sure if I understand. But it seems like you also have to include the API Interface Method name to make the URI [complete](https://stackoverflow.com/questions/56580535/how-to-make-call-to-grpc-server-over-http-1-1-from-curl-command-or-in-internet-b#comment140118404_79102778).
From https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md#requests: > `Path → ":path" "/" Service-Name "/" {method name} ; But see note below.` > > Path is case-sensitive. Some gRPC implementations may allow the Path format shown...
I'm a bit hesitant about making a PR just yet. I have the feeling like something is missing. > Yeah, we'll have a lot of irrelevant results when typing something...
Do you have any thoughts on codegen for golang/elixir/whatever? Would be super good if we could use something as effective as Rust traits but for different languages.
The advantage of the immediate `.into_response()` call is that you can reference data owned by the current function like this: ```rust pub struct Book impl IntoResponse { let local_string: String...