?vL<ddZdZGddeZGddeZGddeZGdd eZy ) aeDEPRECATED: Declares the RPC service interfaces. This module declares the abstract interfaces underlying proto2 RPC services. These are intended to be independent of any particular RPC implementation, so that proto2 services can be used on top of a variety of implementations. Starting with version 2.3.0, RPC implementations should not try to build on these, but should instead provide code generator plugins which generate code specific to the particular RPC implementation. This way the generated code can be more appropriate for the implementation in use and can avoid unnecessary layers of indirection. zpetar@google.com (Petar Petrov)ceZdZdZy) RpcExceptionz4Exception raised on failed blocking RPC method call.N)__name__ __module__ __qualname____doc__Returns true if the call failed. After a call has finished, returns true if the call failed. The possible reasons for failure depend on the RPC implementation. Failed() must not be called before a call has finished. If Failed() returns true, the contents of the response message are undefined. rr"s r FailedzRpcController.Failedws  r ct)zEIf Failed is true, returns a human-readable description of the error.rr"s r ErrorTextzRpcController.ErrorTextrr ct)aInitiate cancellation. Advises the RPC system that the caller desires that the RPC call be canceled. The RPC system may cancel it immediately, may wait awhile and then cancel it, or may not even cancel the call at all. If the call is canceled, the "done" callback will still be called and the RpcController will indicate that the call failed at that time. rr"s r StartCancelzRpcController.StartCancel  r ct)aWSets a failure reason. Causes Failed() to return true on the client side. "reason" will be incorporated into the message returned by ErrorText(). If you find you need to return machine-readable information about failures, you should incorporate it into your response protocol buffer and should NOT call SetFailed(). r)rreasons r SetFailedzRpcController.SetFailedr*r ct)zChecks if the client cancelled the RPC. If true, indicates that the client canceled the RPC, so the server may as well give up on replying to it. The server should still call the final "done" callback. rr"s r IsCanceledzRpcController.IsCanceledrr ct)aSets a callback to invoke on cancel. Asks that the given callback be called when the RPC is canceled. The callback will always be called exactly once. If the RPC completes without being canceled, the callback will be called after completion. If the RPC has already been canceled when NotifyOnCancel() is called, the callback will be called immediately. NotifyOnCancel() must be called no more than once per request. r)rcallbacks r NotifyOnCancelzRpcController.NotifyOnCancels  r N) rrrrr#r%r'r)r-r/r2rr r r r as*   r r ceZdZdZdZy) RpcChannela4Abstract interface for an RPC channel. An RpcChannel represents a communication line to a service which can be used to call that service's methods. The service may be running on another machine. Normally, you should not use an RpcChannel directly, but instead construct a stub {@link Service} wrapping it. Example: Example: RpcChannel channel = rpcImpl.Channel("remotehost.example.com:1234") RpcController controller = rpcImpl.Controller() MyService service = MyService_Stub(channel) service.MyMethod(controller, request, callback) ct)abCalls the method identified by the descriptor. Call the given method of the remote service. The signature of this procedure looks the same as Service.CallMethod(), but the requirements are less strict in one important way: the request object doesn't have to be of any specific class as long as its descriptor is method.input_type. r)rrrrresponse_classrs r rzRpcChannel.CallMethodr*r N)rrrrrrr r r4r4s   r r4N)r __author__ Exceptionrobjectr r r4rr r r:sG / 9 BfBJPFPfr