Lines Matching +full:cancel +full:- +full:in +full:- +full:progress

1 // Protocol Buffers - Google's data interchange format
3 // https://developers.google.com/protocol-buffers/
5 // Redistribution and use in source and binary forms, with or without
11 //     * Redistributions in binary form must reproduce the above
13 // in the documentation and/or other materials provided with the
22 // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
27 // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
28 // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
41 // the generated code can be more appropriate for the implementation in use
48 // A stub is just a type-safe wrapper around an RpcChannel which emulates a
62 //     // implements MyService ---------------------------------------
68 //       // ... read request and fill in response ...
69 //       done->Run();
84 //   // ... fill in request ...
88 // On Thread-Safety:
96 // use a single-threaded RPC system while high-end software will want to
116 // Defined in this file.
121 // Defined in other files.
127 // Abstract base interface for protocol-buffer-based RPC services.  Services
150   // * method->service() == GetDescriptor()
158   //   RpcChannel which the stub is using.  Server-side Service
160   //   the server-side RPC implementation uses.
164   //   before CallMethod() returns or it may be at some point in the future.
174   // CallMethod() requires that the request and response passed in are of a
182   //     service->GetDescriptor()->FindMethodByName("Foo");
183   //   Message* request  = stub->GetRequestPrototype (method)->New();
184   //   Message* response = stub->GetResponsePrototype(method)->New();
185   //   request->ParseFromString(input);
186   //   service->CallMethod(method, *request, response, callback);
198 // RPC implementation and to find out about RPC-level errors.
209   // Client-side methods ---------------------------------------------
213   // Resets the RpcController to its initial state so that it may be reused in
214   // a new call.  Must not be called while an RPC is in progress.
223   // If Failed() is true, returns a human-readable description of the error.
227   // canceled.  The RPC system may cancel it immediately, may wait awhile and
228   // then cancel it, or may not even cancel the call at all.  If the call is
233   // Server-side methods ---------------------------------------------
239   // you need to return machine-readable information about failures, you
269 //   service->MyMethod(request, &response, callback);
277   // are less strict in one important way:  the request and response objects
279   // method->input_type() and method->output_type().