RFC: rpcss skeleton prototype #2
ovehk at ping.uio.no
Mon Nov 4 17:04:07 CST 2002
On Mon, 4 Nov 2002, Greg Turner wrote:
> ATM that's largely correct, except it should also support a "daemon"
> mode ("/s" command-line argument). For local RPC's, the "lazy" (from
> rpcrt4.dll) invocation method will be enough. But -- to be a "real,"
> fully functional RPC server, we will need it running in "server" mode.
> Otherwise, networked RPC's, from without, will always fail, finding no
> endpoint mapper or name service to converse with at the local host.
Note that to be a "real, fully functional RPC server", it would have to
bind to a privileged port and such, providing all the DCE RPC daemon
services that should live on that port. I'm not sure I would trust a
complex Winelib app to run as root, listening on an open network port.
It'd probably be much better to let the user run a real DCE RPC daemon
(like freedce's) as root, and just have Wine's rpcss communicate with it
as necessary to update this real daemon's registrations. Then several
(Unix) users could run RPC services on the same host, too.
(Doesn't solve the problem with remote activation, though)
More information about the wine-devel