Searched refs:messages (Results 1 – 15 of 15) sorted by relevance
39 // messages to a topic.72 option (google.api.method_signature) = "topic,messages";158 // The encoding of messages validated against `schema`.188 // to messages published on this topic.274 // Required. The messages to publish.654 // will pull and ack messages using API methods.1124 // stops sending more messages. The sending of messages resumes once the1135 // server will stop sending more messages. The sending of messages resumes1145 // messages from the server to the client.1147 // Received Pub/Sub messages. This will not be empty.[all …]
271 // The encoding expected for messages278 // Possible encoding types for messages.
228 let messages = std::iter::repeat_with(move || Ok::<_, Status>(msg.clone())).take(10000); in encode() localVariable229 let source = tokio_stream::iter(messages); in encode()250 let messages = std::iter::once(Ok::<_, Status>(msg)); in encode_max_message_size_exceeded() localVariable251 let source = tokio_stream::iter(messages); in encode_max_message_size_exceeded()287 let messages = std::iter::once(Ok::<_, Status>(msg)); in encode_too_big() localVariable288 let source = tokio_stream::iter(messages); in encode_too_big()
72 // get: "/v1/{name=messages/*}"87 // `GET /v1/messages/123456` | `GetMessage(name: "messages/123456")`96 // get:"/v1/messages/{message_id}"113 // `GET /v1/messages/123456?revision=2&sub.subfield=foo` |131 // patch: "/v1/messages/{message_id}"147 // `PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:158 // patch: "/v1/messages/{message_id}"188 // get: "/v1/messages/{message_id}"190 // get: "/v1/users/{user_id}/messages/{message_id}"204 // `GET /v1/messages/123456` | `GetMessage(message_id: "123456")`[all …]
29 // in protobuf messages.
20 // messages in your project. A typical example is to use it as argument or the
21 import "messages.proto";
1 // Benchmark messages for proto3.
97 // Serialized FileDescriptorProto messages sent by the server answering101 // Serialized FileDescriptorProto messages. We avoid taking a dependency on
107 // Serialized FileDescriptorProto messages sent by the server answering111 // Serialized FileDescriptorProto messages. We avoid taking a dependency on
44 // A list of messages that carry the error details. There is a common set of
116 to read a sequence of messages back. The client reads from the returned stream until there are117 no more messages. As you can see in our example, you specify a server-side streaming method by127 - A *client-side streaming RPC* where the client writes a sequence of messages and sends them to128 the server. Once the client has finished writing the messages, it waits for the server to read them137 - A *bidirectional streaming RPC* where both sides send a sequence of messages. The two streams139 order they like: for example, the server could wait to receive all the client messages before141 combination of reads and writes. The order of messages in each stream is preserved. You specify683 no more messages left in the stream.
63 …es we used above in our `SayHello` RPC method. RPC types are defined as messages which contain typ…
112 vector of standard error messages that will be generated or that was received,
67 * **tonic:** flush accumulated ready messages when status received ([#1756](https://github.com/hype…112 * **web:** Buffer incomplete messages ([#1528](https://github.com/hyperium/tonic/issues/1528)) ([fe…127 * **core:** amortize many ready messages into fewer, larger buffers ([#1423](https://github.com/hyp…