dce/rpc "client" api

[Luke Kenneth Casson Leighton]

On Fri, 18 Aug 2000, Peter Samuelson wrote:

> 
> [lkcl]
> > i intend to write a... a... [think-of-a-name,quick!] dcetcpd "thing"
> > which will be incredibly simple.  it will listen on a TCP port, it
> > will send an "anonymous credentials setup" over ncalrpc, and from
> > then on it will simply read_data() followed by write_data() and
> > vice-versa to communicate between the TCP socket and the unix domain
> > socket.
> 
> Uh, what for?  Is this so that a given rpc server only needs to bind to
> one net source (the domain socket)?

yes, basically.

otherwise, a similar transport-independent "server" api will be required.
that, i think, is particularly tricky to do in a dynamic fashion.  how
would it be possible?  i cannot actually think of a suitable mechanism!

one proposal for samba to implement [reimplement?] is to merge all the
dce/rpc services *back* into smbd.  whilst this has the advantage of
sharing code, it means that the smbd binary approximately doubles in size,
and will keep on increasing for every extra dce/rpc service that is added
to it.  the samba "file and print" server then becomes a monster :)

another is to use a .so mechanism.  smbd would "load" the .so required
[e.g netlogon.so] at run-time.