Network Working Group:Nat Brown
INTERNET-DRAFT:Charlie Kindel
Expires in six months:January, 1998
This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt" listing contained in the internet-drafts Shadow Directories at <ftp://ftp.is.co.za/internet-drafts> (Africa), <ftp://nic.nordu.net/internet-drafts> (Europe), <ftp://munnari.oz.au/internet-drafts> (Pacific Rim), <ftp://ds.internic.net/internet-drafts> (US East Coast), or <ftp://ftp.isi.edu/internet-drafts> (US West Coast).
Distribution of this document is unlimited. Please send comments to the authors at <mailto:oleidea@microsoft.com>. General discussions about DCOM and its applications should take place on the DCOM mailing list. To subscribe, write to <mailto:LISTSERV@listserv.msn.com> with message body: Subscribe DCOM
You'll receive a Command Confirmation message you must reply to, following instructions in that message. You'll then receive a Welcome message when your subscription has been processed. The Welcome message explains how to change to a digest subscription and unsubscribe. For assistance with the mailing list write to DCOM-request@LISTSERV.MSN.COM.
The Distributed Component Object Model protocol is an application-level protocol for object-oriented remote procedure calls useful for distributed, component-based systems of all types. It is a generic protocol layered on the distributed computing environment (DCE) RPC specification and facilitates the construction of task-specific communication protocols through features such as: a platform neutral argument/parameter marshaling format (NDR), the ability for objects to support multiple interfaces with a safe, interface-level versioning scheme suited to independent evolution by multiple parties, the ability to make authenticated connections and to choose levels of channel security, and a transport-neutral data representation for references (including by-value) to objects.