Lines Matching defs:Service
45 // When you use the protocol compiler to compile a service definition, it
46 // generates two classes: An abstract interface for the service (with
47 // methods matching the service definition) and a "stub" implementation.
49 // local implementation of the service.
51 // For example, the service definition:
52 // service MyService {
111 class Service;
124 // interface can be used to call the methods of the Service without knowing
126 class LIBPROTOBUF_EXPORT Service {
128 inline Service() {}
129 virtual ~Service();
139 // Get the ServiceDescriptor describing this service and its methods.
142 // Call a method of the service specified by MethodDescriptor. This is
144 // definitions of the service's methods.
147 // * method->service() == GetDescriptor()
154 // used by this Service. For stubs, the "correct type" depends on the
155 // RpcChannel which the stub is using. Server-side Service
181 // service->GetDescriptor()->FindMethodByName("Foo");
185 // service->CallMethod(method, *request, response, callback);
192 GOOGLE_DISALLOW_EVIL_CONSTRUCTORS(Service);
262 // communication line to a Service which can be used to call that Service's
263 // methods. The Service may be running on another machine. Normally, you
264 // should not call an RpcChannel directly, but instead construct a stub Service
267 // MyService* service = new MyService::Stub(channel);
268 // service->MyMethod(request, &response, callback);
274 // Call the given method of the remote service. The signature of this
275 // procedure looks the same as Service::CallMethod(), but the requirements
