Remotely, DCOM uses DCERPC, apparently with some tweaks for DGC, interface negotiation, and NTLM security. Between apartments, COM uses plain old USER32 window messages (a STA thread has to pump messages or none of its objects can receive messages or responses). Within an apartment, COM permits calls right through the object's vtbl. I'm sure you could write a custom marshaller that uses NetBIOS (or more likely NetBIOS over TCP) named pipes, but AFAIK neither Microsoft nor anyone else has shipped a (D)COM object that does so by default.
Fair use isn't an affirmative right, but the Association of Research Libraries timeline says when copyright law was was heavily revised in 1976, fair use became an official defense against infringement charges--though what's allowed and what isn't is only somewhat less vague than when courts were simply disregarding some benign infrinements (which seems ironically similar to jury nullification).
Unfortunately, the Classic process has complete access to the network and all files the current user is allowed to modify (and for a single user system, that's everything of value). This is why we should be using capability-based systems, so we don't have to blindly delegate all our privileges to everything we run, even if we don't really trust it.
Slashdot Mirror
Remotely, DCOM uses DCERPC, apparently with some tweaks for DGC, interface negotiation, and NTLM security. Between apartments, COM uses plain old USER32 window messages (a STA thread has to pump messages or none of its objects can receive messages or responses). Within an apartment, COM permits calls right through the object's vtbl. I'm sure you could write a custom marshaller that uses NetBIOS (or more likely NetBIOS over TCP) named pipes, but AFAIK neither Microsoft nor anyone else has shipped a (D)COM object that does so by default.
Fair use isn't an affirmative right, but the Association of Research Libraries timeline says when copyright law was was heavily revised in 1976, fair use became an official defense against infringement charges--though what's allowed and what isn't is only somewhat less vague than when courts were simply disregarding some benign infrinements (which seems ironically similar to jury nullification).
Unfortunately, the Classic process has complete access to the network and all files the current user is allowed to modify (and for a single user system, that's everything of value). This is why we should be using capability-based systems, so we don't have to blindly delegate all our privileges to everything we run, even if we don't really trust it.