Home
last modified time | relevance | path

Searched refs:methods (Results 1 – 15 of 15) sorted by relevance

/tonic/tonic-build/src/
H A Dmanual.rs65 methods: Vec<Method>, field
96 self.methods.push(method); in method()
108 methods: self.methods, in build()
123 methods: Vec<Method>, field
150 fn methods(&self) -> &[Self::Method] { in methods() method
151 &self.methods in methods()
H A Dprost.rs75 methods: Vec<TonicBuildMethod>, field
83 methods: prost_service in new()
84 .methods in new()
122 fn methods(&self) -> &[Self::Method] { in methods() method
123 &self.methods in methods()
H A Dserver.rs23 let methods = generate_methods( in generate_internal() localVariable
165 #methods in generate_internal()
207 let methods = generate_trait_methods( in generate_trait() localVariable
225 #methods in generate_trait()
241 for method in service.methods() { in generate_trait_methods()
379 for method in service.methods() { in generate_methods()
H A Dclient.rs22 let methods = generate_methods( in generate_internal() localVariable
133 #methods in generate_internal()
176 for method in service.methods() { in generate_methods()
H A Dlib.rs117 fn methods(&self) -> &[Self::Method]; in methods() method
/tonic/tonic-types/
H A DREADME.md16 be returned to gRPC clients. Moreover, the trait also adds methods to
107 ## Alternative `tonic::Status` associated functions and methods
118 methods are provided in the [`StatusExt`] doc, which can be specially
/tonic/examples/proto/googleapis/google/api/
H A Dhttp.proto28 // to one or more HTTP REST API methods.
30 // A list of HTTP configuration rules that apply to individual API methods.
124 // For HTTP methods that allow a request body, the `body` field
179 // defining REST APIs. The common usage of `*` is in custom methods
182 // It is possible to define multiple HTTP methods for one RPC by using
320 // used with any of the {get|put|post|delete|patch} methods. A custom method
H A Dclient.proto30 // In client libraries, each proto RPC corresponds to one or more methods
/tonic/examples/
H A Drouteguide-tutorial.md104 Then you define `rpc` methods inside your service definition, specifying their request and response
150 response types used in our service methods - for example, here's the `Point` message type:
368 All our service methods receive a `tonic::Request<T>` and return a
369 `Result<tonic::Response<T>, tonic::Status>`. The concrete type of `T` depends on how our methods
530 Once we've implemented all our methods, we also need to start up a gRPC server so that clients can
558 methods.
591 To call service methods, we first need to create a gRPC *client* to communicate with the server. Li…
619 ### Calling service methods
620 Now let's look at how we call our service methods. Note that in Tonic, RPCs are asynchronous,
H A Dhelloworld-tutorial.md42 Then you define RPC methods inside your service definition, specifying their request and response
43 types. gRPC lets you define four kinds of service methods, all of which are supported by Tonic. For…
271 The client is much simpler than the server as we don't need to implement any service methods, just …
/tonic/interop/proto/grpc/testing/
H A Dtest.proto63 // to test the behavior when clients call unimplemented methods.
/tonic/tonic-reflection/proto/
H A Dreflection_v1alpha.proto33 // defined field and then handles them using corresponding methods.
H A Dreflection_v1.proto43 // defined field and then handles them using corresponding methods.
/tonic/
H A DCHANGELOG.md6 * **build:** Add `#[deprecated]` to deprecated client methods (#1879)
515 * **transport:** Add optional service methods ([#275](https://github.com/hyperium/tonic/issues/275)…
/tonic/examples/proto/googleapis/google/pubsub/v1/
H A Dpubsub.proto654 // will pull and ack messages using API methods.