Home
last modified time | relevance | path

Searched refs:clients (Results 1 – 13 of 13) sorted by relevance

/tonic/tonic-build/src/
H A Dmanual.rs357 clients: TokenStream, field
379 self.clients.extend(client); in generate()
384 if self.builder.build_client && !self.clients.is_empty() { in finalize()
385 let clients = &self.clients; in finalize() localVariable
388 #clients in finalize()
395 self.clients = TokenStream::default(); in finalize()
487 clients: TokenStream::default(), in compile()
H A Dprost.rs207 clients: TokenStream, field
215 clients: TokenStream::default(), in new()
251 self.clients.extend(client); in generate()
256 if self.builder.build_client && !self.clients.is_empty() { in finalize()
257 let clients = &self.clients; in finalize() localVariable
260 #clients in finalize()
267 self.clients = TokenStream::default(); in finalize()
/tonic/tonic-web/
H A DREADME.md3 Enables tonic servers to handle requests from `grpc-web` clients directly,
/tonic/tonic-health/proto/
H A Dhealth.proto58 // If the call terminates with status UNIMPLEMENTED, then clients
61 // clients should retry the call with appropriate exponential backoff.
/tonic/examples/
H A DREADME.md159 Both clients and both servers do the same thing, but using the two different
160 approaches. Run one of the servers in one terminal, and then run the clients
H A Drouteguide-tutorial.md20 Our example is a simple route mapping application that lets clients get information about features
22 updates with the server and other clients.
24 With gRPC we can define our service once in a `.proto` file and implement clients and servers in
138 operate independently, so clients and servers can read and write in whatever
218 clients, you can skip this section and go straight to [Creating the client](#client)
224 - Running a gRPC server to listen for requests from clients.
530 Once we've implemented all our methods, we also need to start up a gRPC server so that clients can
798 - When building rust clients and servers in different crates.
/tonic/interop/proto/grpc/testing/
H A Dtest.proto63 // to test the behavior when clients call unimplemented methods.
67 // A simple service NOT implemented at servers so clients can test for
H A Dmessages.proto46 // clients to specify a status that the server should attempt to return.
72 // "nullable" in order to interoperate seamlessly with clients not able to
125 // "nullable" in order to interoperate seamlessly with clients not able to
/tonic/tonic-types/proto/
H A Derror_details.proto27 // Describes when the clients can retry a failed request. Clients could ignore
31 // It's always recommended that clients should use exponential backoff when
36 // fail, clients should use an exponential backoff scheme to gradually increase
186 // Contains metadata about the request that clients can attach when filing a bug
/tonic/
H A DREADME.md21 contains the tools to build clients and servers from [`protobuf`] definitions.
H A DCHANGELOG.md26 * **channel:** Re-enable TLS based on Cargo features in generated clients (#1866)
232 * Add `Grpc::with_origin` for clients ([#1017](https://github.com/hyperium/tonic/issues/1017)) ([10…
384 * **build:** support adding attributes to clients and servers ([#684](https://github.com/hyperium/t…
629 * expose tcp_nodelay for clients and servers ([#145](https://github.com/hyperium/tonic/issues/145))…
636 * **transport:** Expose tcp keepalive to clients & servers ([#151](https://github.com/hyperium/toni…
/tonic/tonic-types/
H A DREADME.md16 be returned to gRPC clients. Moreover, the trait also adds methods to
/tonic/examples/proto/googleapis/google/api/
H A Dhttp.proto342 // for services that provide content to Web (HTML) clients.