outsourcing DCE/RPC to alternate programs - runtime config option

[Luke Kenneth Casson Leighton]

> transports at all. As a single ncacn_np pipe name is often used to
> handle many rpc interfaces (such as with lsass), 

 are you sure that you're not confusing interface versioning
 with something else?

 remember that DCE/RPC supports the concept of upgradeable interfaces
 (don't ask me _how_ i just know it can be done!)

 so if you add an extra function to the lsass interface (which has been
 done at least once) then you register a new uuid and give it an uprated
 version number.

 on startup of the LSASS.EXE service, the DCE/RPC runtime
 registers with the epmapper on your behalf the fact that you
 support many versions of the same service (with different
 uuids) on the same endpoint (ncacn_np://server/lsass).

 i can't tell you _how_ that's all handled because i've never written a
 DCE/RPC application which does it.

 perhaps someone at the opendce list will know?

 ta,

 l.