Merge "Cleaned up references to executor specific RPCServer types"
This commit is contained in:
commit
1b4d7ad6f2
|
@ -40,9 +40,6 @@ RPC servers have start(), stop() and wait() messages to begin handling
|
|||
requests, stop handling requests and wait for all in-process requests to
|
||||
complete.
|
||||
|
||||
An RPC server class is provided for each supported I/O handling framework.
|
||||
Currently BlockingRPCServer and eventlet.RPCServer are available.
|
||||
|
||||
A simple example of an RPC server with multiple endpoints might be::
|
||||
|
||||
from oslo.config import cfg
|
||||
|
@ -70,7 +67,8 @@ A simple example of an RPC server with multiple endpoints might be::
|
|||
ServerControlEndpoint(self),
|
||||
TestEndpoint(),
|
||||
]
|
||||
server = messaging.get_rpc_server(transport, target, endpoints)
|
||||
server = messaging.get_rpc_server(transport, target, endpoints,
|
||||
executor='eventlet')
|
||||
server.start()
|
||||
server.wait()
|
||||
|
||||
|
|
|
@ -107,9 +107,7 @@ class MessageHandlingServer(object):
|
|||
process, thread or co-operatively scheduled coroutine or simply by
|
||||
registering a callback with an event loop. Similarly, the executor may
|
||||
choose to dispatch messages in a new thread, coroutine or simply the
|
||||
current thread. An RPCServer subclass is available for each I/O
|
||||
strategy supported by the library, so choose the subclass appropriate
|
||||
for your program.
|
||||
current thread.
|
||||
"""
|
||||
if self._executor is not None:
|
||||
return
|
||||
|
|
Loading…
Reference in New Issue