RPC client/server connections
ovek at arcticnet.no
Sat Feb 15 18:00:59 CST 2003
For better concurrency, this patch separates the connections from the
For RPC clients, a new RPC client connection is grabbed for every RPC
call, and released when the call ends. This allows multiple RPC calls to
happen simultaneously using the same binding (and is in fact how this is
supposed to work, as far as I can tell from the freedce sources), but
since we don't have a connection cache yet this is going to be somewhat
inefficient (a connection will be opened and closed for every RPC call).
Oh well, at least it works for me this way.
And RPC servers now work with connections, not bindings, bindings are
now created dynamically for every incoming RPC call. RPC calls are also
now dispatched to worker threads, so more than one call can be processed
simultaneously on the same connection (if we can reliably multiplex
multiple calls on the same connection on the client side, that is).
Ove Kaaven <ovek at transgaming.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 43261 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20030216/8d5963c3/rpc0.bin
More information about the wine-patches