On Thursday 30 October 2003 04:16 pm, Mike Hearn wrote:
ncalrpc?
The preferred transport for local-to-self RPC/DCOM communications. In NT it's implemented on top of "NT Ports" (see Undocumented NT), the advantge being that this is fast. This RPC transport (but not the NT ports themselves) is simulated using named pipes in wine.
For example, see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/midl/midl/n...
The whole family is nicely summarized here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rpc/rpc/str...
Sheesh, so much to do... it's enough to make me want to finish my cabinet work rather than confront it ;)
BTW, note that transports like http, tcp, etc, could allow wine to do DCOM without resolving the "priveleged ports" issue (at least for fixed endpoints).... of course, our wire protocol is way off and will need fixing before that's possible... luckily I have archived the spec (enclosed for your amusement), which AFAIK fell off the 'net. Older revisions are available by searching (<a href="http://www.brassroots.org/google.html">do not Google!</a>) the 'net; the enclosed version was linked to by Don Box's delicious blog back when it existed at http://www.globecom.net/ietf/draft/draft-brown-dcom-v1-spec-03.html.