Distributed Component Object Model - Revision history

Dicklyon: rm inappropriate hatnote

2025-04-22T03:29:27Z

rm inappropriate hatnote

← Previous revision		Revision as of 03:29, 22 April 2025
Line 1:		Line 1:
	{{Short description\|Software for communication between software components}}		{{Short description\|Software for communication between software components}}

	~~{{Redirect\|Dcom\|the doctoral degree\|Doctor of Commerce\|other uses\|DCOM (disambiguation)}}~~'''Distributed Component Object Model''' ('''DCOM''') is a [[proprietary software\|proprietary]] [[Microsoft]] technology for communication between [[software componentry\|software components]] on networked [[computer]]s. DCOM, which originally was called "Network [[Object Linking and Embedding\|OLE]]", extends Microsoft's [[Component Object Model\|COM]], and provides the communication substrate under Microsoft's [[Component Object Model#COM+\|COM+]] application server infrastructure.		'''Distributed Component Object Model''' ('''DCOM''') is a [[proprietary software\|proprietary]] [[Microsoft]] technology for communication between [[software componentry\|software components]] on networked [[computer]]s. DCOM, which originally was called "Network [[Object Linking and Embedding\|OLE]]", extends Microsoft's [[Component Object Model\|COM]], and provides the communication substrate under Microsoft's [[Component Object Model#COM+\|COM+]] application server infrastructure.

	The extension COM into Distributed COM was due to extensive use of [[DCE/RPC]] (Distributed Computing Environment/Remote Procedure Calls) – more specifically Microsoft's enhanced version, known as [[MSRPC]]. <ref>{{Cite web \|title=What is Distributed Component Object Model (DCOM)? \|url=https://www.techtarget.com/whatis/definition/DCOM-Distributed-Component-Object-Model \|access-date=2022-08-03 \|website=WhatIs.com \|language=en}}</ref>		The extension COM into Distributed COM was due to extensive use of [[DCE/RPC]] (Distributed Computing Environment/Remote Procedure Calls) – more specifically Microsoft's enhanced version, known as [[MSRPC]]. <ref>{{Cite web \|title=What is Distributed Component Object Model (DCOM)? \|url=https://www.techtarget.com/whatis/definition/DCOM-Distributed-Component-Object-Model \|access-date=2022-08-03 \|website=WhatIs.com \|language=en}}</ref>

Winderz IoT: Ref fix

2025-01-04T00:53:46Z

Ref fix

← Previous revision		Revision as of 00:53, 4 January 2025
Line 11:		Line 11:
	One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who is responsible for freeing memory.<ref>{{Cite web \|title=DCE 1.1: Remote Procedure Call - Introduction to the RPC API \|url=https://pubs.opengroup.org/onlinepubs/9629399/chap2.htm \|access-date=2022-08-03 \|website=pubs.opengroup.org}}</ref>		One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who is responsible for freeing memory.<ref>{{Cite web \|title=DCE 1.1: Remote Procedure Call - Introduction to the RPC API \|url=https://pubs.opengroup.org/onlinepubs/9629399/chap2.htm \|access-date=2022-08-03 \|website=pubs.opengroup.org}}</ref>

	DCOM was a major competitor to [[CORBA]].<ref>{{Cite ~~journal~~ \|last1=Nowak \|first1=Filip \|last2=Qasim \|first2=Mohsin \|title=A Comparison of Distributed Object Technologies CORBA vs DCOM \|url=https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-url=https://web.archive.org/web/20170829054415/https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-date=2017-08-29 \|url-status=live \|journal=}}</ref> Proponents of both of these technologies saw them as one day becoming the model for code and service-reuse over the [[Internet]]. However, the difficulties involved in getting either of these technologies to work over Internet [[Firewall (networking)\|firewalls]], and on unknown and insecure machines, meant that normal [[HTTP]] requests in combination with [[web browser]]s won out over both of them.<ref>{{Cite web \|title=Object Technology Jeff Sutherland: Web Services: Better than CORBA or DCOM? \|url=http://jeffsutherland.com/2003/10/web-services-better-than-corba-or-dcom.html \|access-date=2022-08-03 \|language=en}}</ref> Microsoft, at one point, attempted to remediate these shortcomings by adding an extra HTTP transport to DCE/RPC called ''ncacn_http'' (Network Computing Architecture connection-oriented protocol).<ref>{{Cite web \|last=stevewhims \|title=Remote Procedure Calls Using RPC over HTTP - Win32 apps \|url=https://docs.microsoft.com/en-us/windows/win32/rpc/remote-procedure-calls-using-rpc-over-http \|access-date=2022-08-03 \|website=docs.microsoft.com \|date=23 August 2019 \|language=en-us}}</ref>		DCOM was a major competitor to [[CORBA]].<ref>{{Cite web \|last1=Nowak \|first1=Filip \|last2=Qasim \|first2=Mohsin \|title=A Comparison of Distributed Object Technologies CORBA vs DCOM \|url=https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-url=https://web.archive.org/web/20170829054415/https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-date=2017-08-29 \|url-status=live \|journal=}}</ref> Proponents of both of these technologies saw them as one day becoming the model for code and service-reuse over the [[Internet]]. However, the difficulties involved in getting either of these technologies to work over Internet [[Firewall (networking)\|firewalls]], and on unknown and insecure machines, meant that normal [[HTTP]] requests in combination with [[web browser]]s won out over both of them.<ref>{{Cite web \|title=Object Technology Jeff Sutherland: Web Services: Better than CORBA or DCOM? \|url=http://jeffsutherland.com/2003/10/web-services-better-than-corba-or-dcom.html \|access-date=2022-08-03 \|language=en}}</ref> Microsoft, at one point, attempted to remediate these shortcomings by adding an extra HTTP transport to DCE/RPC called ''ncacn_http'' (Network Computing Architecture connection-oriented protocol).<ref>{{Cite web \|last=stevewhims \|title=Remote Procedure Calls Using RPC over HTTP - Win32 apps \|url=https://docs.microsoft.com/en-us/windows/win32/rpc/remote-procedure-calls-using-rpc-over-http \|access-date=2022-08-03 \|website=docs.microsoft.com \|date=23 August 2019 \|language=en-us}}</ref>

	DCOM was publicly launched as a beta for Windows 95 September 18, 1996.<ref>[https://news.microsoft.com/1996/09/18/microsoft-releases-beta-version-of-dcom-for-windows-95/#Microsoft Press Release Announcing DCOM Beta]</ref>		DCOM was publicly launched as a beta for Windows 95 September 18, 1996.<ref>[https://news.microsoft.com/1996/09/18/microsoft-releases-beta-version-of-dcom-for-windows-95/#Microsoft Press Release Announcing DCOM Beta]</ref>

Citation bot: Add: publisher, date, authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | Category:Object models | #UCB_Category 12/12

2024-11-20T17:04:29Z

Add: publisher, date, authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | Category:Object models | #UCB_Category 12/12

← Previous revision		Revision as of 17:04, 20 November 2024
Line 11:		Line 11:
	One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who is responsible for freeing memory.<ref>{{Cite web \|title=DCE 1.1: Remote Procedure Call - Introduction to the RPC API \|url=https://pubs.opengroup.org/onlinepubs/9629399/chap2.htm \|access-date=2022-08-03 \|website=pubs.opengroup.org}}</ref>		One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who is responsible for freeing memory.<ref>{{Cite web \|title=DCE 1.1: Remote Procedure Call - Introduction to the RPC API \|url=https://pubs.opengroup.org/onlinepubs/9629399/chap2.htm \|access-date=2022-08-03 \|website=pubs.opengroup.org}}</ref>

	DCOM was a major competitor to [[CORBA]].<ref>{{Cite journal \|~~last~~=Nowak \|~~first~~=Filip \|last2=Qasim \|first2=Mohsin \|title=A Comparison of Distributed Object Technologies CORBA vs DCOM \|url=https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-url=https://web.archive.org/web/20170829054415/https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-date=2017-08-29 \|url-status=live \|journal=}}</ref> Proponents of both of these technologies saw them as one day becoming the model for code and service-reuse over the [[Internet]]. However, the difficulties involved in getting either of these technologies to work over Internet [[Firewall (networking)\|firewalls]], and on unknown and insecure machines, meant that normal [[HTTP]] requests in combination with [[web browser]]s won out over both of them.<ref>{{Cite web \|title=Object Technology Jeff Sutherland: Web Services: Better than CORBA or DCOM? \|url=http://jeffsutherland.com/2003/10/web-services-better-than-corba-or-dcom.html \|access-date=2022-08-03 \|language=en}}</ref> Microsoft, at one point, attempted to remediate these shortcomings by adding an extra HTTP transport to DCE/RPC called ''ncacn_http'' (Network Computing Architecture connection-oriented protocol).<ref>{{Cite web \|last=stevewhims \|title=Remote Procedure Calls Using RPC over HTTP - Win32 apps \|url=https://docs.microsoft.com/en-us/windows/win32/rpc/remote-procedure-calls-using-rpc-over-http \|access-date=2022-08-03 \|website=docs.microsoft.com \|language=en-us}}</ref>		DCOM was a major competitor to [[CORBA]].<ref>{{Cite journal \|last1=Nowak \|first1=Filip \|last2=Qasim \|first2=Mohsin \|title=A Comparison of Distributed Object Technologies CORBA vs DCOM \|url=https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-url=https://web.archive.org/web/20170829054415/https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-date=2017-08-29 \|url-status=live \|journal=}}</ref> Proponents of both of these technologies saw them as one day becoming the model for code and service-reuse over the [[Internet]]. However, the difficulties involved in getting either of these technologies to work over Internet [[Firewall (networking)\|firewalls]], and on unknown and insecure machines, meant that normal [[HTTP]] requests in combination with [[web browser]]s won out over both of them.<ref>{{Cite web \|title=Object Technology Jeff Sutherland: Web Services: Better than CORBA or DCOM? \|url=http://jeffsutherland.com/2003/10/web-services-better-than-corba-or-dcom.html \|access-date=2022-08-03 \|language=en}}</ref> Microsoft, at one point, attempted to remediate these shortcomings by adding an extra HTTP transport to DCE/RPC called ''ncacn_http'' (Network Computing Architecture connection-oriented protocol).<ref>{{Cite web \|last=stevewhims \|title=Remote Procedure Calls Using RPC over HTTP - Win32 apps \|url=https://docs.microsoft.com/en-us/windows/win32/rpc/remote-procedure-calls-using-rpc-over-http \|access-date=2022-08-03 \|website=docs.microsoft.com \|date=23 August 2019 \|language=en-us}}</ref>

	DCOM was publicly launched as a beta for Windows 95 September 18, 1996.<ref>[https://news.microsoft.com/1996/09/18/microsoft-releases-beta-version-of-dcom-for-windows-95/#Microsoft Press Release Announcing DCOM Beta]</ref>		DCOM was publicly launched as a beta for Windows 95 September 18, 1996.<ref>[https://news.microsoft.com/1996/09/18/microsoft-releases-beta-version-of-dcom-for-windows-95/#Microsoft Press Release Announcing DCOM Beta]</ref>
Line 25:		Line 25:
	'''COMsource''' is a Unix based implementation of DCOM, allowing interoperability between different platforms. Its source code is available, along with full and complete documentation, sufficient to use and also implement an interoperable version of DCOM. COMsource comes directly from the [[Windows NT]] 4.0 source code, and includes the source code for a [[Windows Registry\|Windows NT Registry Service]]. <ref>{{Cite web \|title=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms \|url=http://www.opengroup.org/comsource/datasheet.htm \|website=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms}}</ref>		'''COMsource''' is a Unix based implementation of DCOM, allowing interoperability between different platforms. Its source code is available, along with full and complete documentation, sufficient to use and also implement an interoperable version of DCOM. COMsource comes directly from the [[Windows NT]] 4.0 source code, and includes the source code for a [[Windows Registry\|Windows NT Registry Service]]. <ref>{{Cite web \|title=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms \|url=http://www.opengroup.org/comsource/datasheet.htm \|website=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms}}</ref>

	In 1995, Digital and [[Microsoft]] announced Affinity for OpenVMS (also known as NT Affinity) which was intended to allow OpenVMS to serve as the [[persistence layer]] for Windows NT [[Client–server model\|client-server applications]].<ref name="vms-20-years">{{cite web\|url=https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-url=https://web.archive.org/web/20210419084702/https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-date=2021-04-19 \|url-status=live\|date=October 1997\|title=OpenVMS at 20 Nothing stops it\|publisher=Digital\|access-date=2021-02-12}}</ref> As part of this initiative, an implementation of the Distributed Component Object Model (DCOM) was added to OpenVMS Alpha.<ref name="com-compaq">{{cite book\|title=COM Beyond Microsoft: Designing and Implementing COM Servers on Compaq Platforms\|url=https://books.google.com/books?id=i47yKPSDd1gC\|isbn=1555582265\|author=Gene Cronin, Terence P. Sherlock\|date=2000}}</ref> In order to support DCOM, VMS was provided with implementations of the Windows Registry, [[NTLM]] authentication, and a subset of [[Win32]] APIs needed to support COM.<ref>{{cite web\|url=http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|title=OpenVMS Connectivity Developer Guide\|date=July 2000\|access-date=2021-01-01\|website=hpe.com\|archive-date=2020-12-04\|archive-url=https://web.archive.org/web/20201204205526/http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|url-status=dead}}</ref> DCOM was first added to OpenVMS V7.2-1 for the Alpha.<ref>{{cite web\|url=http://odl.sysworks.biz/disk$vaxdocmar002/opsys/vmsos721/6614/6614pro_contents.html\|title=OpenVMS Alpha V7.2-1 Release Notes\|website=odl.sysworks.biz\|access-date=2021-01-01\|date=January 1999}}</ref> A similar implementation of DCOM was added to [[Digital Unix]] as part of the AllConnect program.<ref name="com-compaq" />		In 1995, Digital and [[Microsoft]] announced Affinity for OpenVMS (also known as NT Affinity) which was intended to allow OpenVMS to serve as the [[persistence layer]] for Windows NT [[Client–server model\|client-server applications]].<ref name="vms-20-years">{{cite web\|url=https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-url=https://web.archive.org/web/20210419084702/https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-date=2021-04-19 \|url-status=live\|date=October 1997\|title=OpenVMS at 20 Nothing stops it\|publisher=Digital\|access-date=2021-02-12}}</ref> As part of this initiative, an implementation of the Distributed Component Object Model (DCOM) was added to OpenVMS Alpha.<ref name="com-compaq">{{cite book\|title=COM Beyond Microsoft: Designing and Implementing COM Servers on Compaq Platforms\|url=https://books.google.com/books?id=i47yKPSDd1gC\|isbn=1555582265\|author=Gene Cronin, Terence P. Sherlock\|date=2000\| publisher=Digital Press }}</ref> In order to support DCOM, VMS was provided with implementations of the Windows Registry, [[NTLM]] authentication, and a subset of [[Win32]] APIs needed to support COM.<ref>{{cite web\|url=http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|title=OpenVMS Connectivity Developer Guide\|date=July 2000\|access-date=2021-01-01\|website=hpe.com\|archive-date=2020-12-04\|archive-url=https://web.archive.org/web/20201204205526/http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|url-status=dead}}</ref> DCOM was first added to OpenVMS V7.2-1 for the Alpha.<ref>{{cite web\|url=http://odl.sysworks.biz/disk$vaxdocmar002/opsys/vmsos721/6614/6614pro_contents.html\|title=OpenVMS Alpha V7.2-1 Release Notes\|website=odl.sysworks.biz\|access-date=2021-01-01\|date=January 1999}}</ref> A similar implementation of DCOM was added to [[Digital Unix]] as part of the AllConnect program.<ref name="com-compaq" />

	'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>		'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>

InternetArchiveBot: Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5) (Whoop whoop pull up - 21816

2024-11-19T15:40:13Z

Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5) (Whoop whoop pull up - 21816

← Previous revision		Revision as of 15:40, 19 November 2024
Line 25:		Line 25:
	'''COMsource''' is a Unix based implementation of DCOM, allowing interoperability between different platforms. Its source code is available, along with full and complete documentation, sufficient to use and also implement an interoperable version of DCOM. COMsource comes directly from the [[Windows NT]] 4.0 source code, and includes the source code for a [[Windows Registry\|Windows NT Registry Service]]. <ref>{{Cite web \|title=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms \|url=http://www.opengroup.org/comsource/datasheet.htm \|website=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms}}</ref>		'''COMsource''' is a Unix based implementation of DCOM, allowing interoperability between different platforms. Its source code is available, along with full and complete documentation, sufficient to use and also implement an interoperable version of DCOM. COMsource comes directly from the [[Windows NT]] 4.0 source code, and includes the source code for a [[Windows Registry\|Windows NT Registry Service]]. <ref>{{Cite web \|title=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms \|url=http://www.opengroup.org/comsource/datasheet.htm \|website=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms}}</ref>

	In 1995, Digital and [[Microsoft]] announced Affinity for OpenVMS (also known as NT Affinity) which was intended to allow OpenVMS to serve as the [[persistence layer]] for Windows NT [[Client–server model\|client-server applications]].<ref name="vms-20-years">{{cite web\|url=https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-url=https://web.archive.org/web/20210419084702/https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-date=2021-04-19 \|url-status=live\|date=October 1997\|title=OpenVMS at 20 Nothing stops it\|publisher=Digital\|access-date=2021-02-12}}</ref> As part of this initiative, an implementation of the Distributed Component Object Model (DCOM) was added to OpenVMS Alpha.<ref name="com-compaq">{{cite book\|title=COM Beyond Microsoft: Designing and Implementing COM Servers on Compaq Platforms\|url=https://books.google.com/books?id=i47yKPSDd1gC\|isbn=1555582265\|author=Gene Cronin, Terence P. Sherlock\|date=2000}}</ref> In order to support DCOM, VMS was provided with implementations of the Windows Registry, [[NTLM]] authentication, and a subset of [[Win32]] APIs needed to support COM.<ref>{{cite web\|url=http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|title=OpenVMS Connectivity Developer Guide		In 1995, Digital and [[Microsoft]] announced Affinity for OpenVMS (also known as NT Affinity) which was intended to allow OpenVMS to serve as the [[persistence layer]] for Windows NT [[Client–server model\|client-server applications]].<ref name="vms-20-years">{{cite web\|url=https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-url=https://web.archive.org/web/20210419084702/https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-date=2021-04-19 \|url-status=live\|date=October 1997\|title=OpenVMS at 20 Nothing stops it\|publisher=Digital\|access-date=2021-02-12}}</ref> As part of this initiative, an implementation of the Distributed Component Object Model (DCOM) was added to OpenVMS Alpha.<ref name="com-compaq">{{cite book\|title=COM Beyond Microsoft: Designing and Implementing COM Servers on Compaq Platforms\|url=https://books.google.com/books?id=i47yKPSDd1gC\|isbn=1555582265\|author=Gene Cronin, Terence P. Sherlock\|date=2000}}</ref> In order to support DCOM, VMS was provided with implementations of the Windows Registry, [[NTLM]] authentication, and a subset of [[Win32]] APIs needed to support COM.<ref>{{cite web\|url=http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|title=OpenVMS Connectivity Developer Guide\|date=July 2000\|access-date=2021-01-01\|website=hpe.com\|archive-date=2020-12-04\|archive-url=https://web.archive.org/web/20201204205526/http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|url-status=dead}}</ref> DCOM was first added to OpenVMS V7.2-1 for the Alpha.<ref>{{cite web\|url=http://odl.sysworks.biz/disk$vaxdocmar002/opsys/vmsos721/6614/6614pro_contents.html\|title=OpenVMS Alpha V7.2-1 Release Notes\|website=odl.sysworks.biz\|access-date=2021-01-01\|date=January 1999}}</ref> A similar implementation of DCOM was added to [[Digital Unix]] as part of the AllConnect program.<ref name="com-compaq" />
	\|date=July 2000\|access-date=2021-01-01\|website=hpe.com}}</ref> DCOM was first added to OpenVMS V7.2-1 for the Alpha.<ref>{{cite web\|url=http://odl.sysworks.biz/disk$vaxdocmar002/opsys/vmsos721/6614/6614pro_contents.html\|title=OpenVMS Alpha V7.2-1 Release Notes\|website=odl.sysworks.biz\|access-date=2021-01-01\|date=January 1999}}</ref> A similar implementation of DCOM was added to [[Digital Unix]] as part of the AllConnect program.<ref name="com-compaq" />

	'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>		'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>

216.164.60.101: Fix capitalization of HTTP

2024-07-13T19:53:19Z

Fix capitalization of HTTP

← Previous revision		Revision as of 19:53, 13 July 2024
Line 11:		Line 11:
	One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who is responsible for freeing memory.<ref>{{Cite web \|title=DCE 1.1: Remote Procedure Call - Introduction to the RPC API \|url=https://pubs.opengroup.org/onlinepubs/9629399/chap2.htm \|access-date=2022-08-03 \|website=pubs.opengroup.org}}</ref>		One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who is responsible for freeing memory.<ref>{{Cite web \|title=DCE 1.1: Remote Procedure Call - Introduction to the RPC API \|url=https://pubs.opengroup.org/onlinepubs/9629399/chap2.htm \|access-date=2022-08-03 \|website=pubs.opengroup.org}}</ref>

	DCOM was a major competitor to [[CORBA]].<ref>{{Cite journal \|last=Nowak \|first=Filip \|last2=Qasim \|first2=Mohsin \|title=A Comparison of Distributed Object Technologies CORBA vs DCOM \|url=https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-url=https://web.archive.org/web/20170829054415/https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-date=2017-08-29 \|url-status=live \|journal=}}</ref> Proponents of both of these technologies saw them as one day becoming the model for code and service-reuse over the [[Internet]]. However, the difficulties involved in getting either of these technologies to work over Internet [[Firewall (networking)\|firewalls]], and on unknown and insecure machines, meant that normal [[HTTP]] requests in combination with [[web browser]]s won out over both of them.<ref>{{Cite web \|title=Object Technology Jeff Sutherland: Web Services: Better than CORBA or DCOM? \|url=http://jeffsutherland.com/2003/10/web-services-better-than-corba-or-dcom.html \|access-date=2022-08-03 \|language=en}}</ref> Microsoft, at one point, attempted to remediate these shortcomings by adding an extra ~~http~~ transport to DCE/RPC called ''ncacn_http'' (Network Computing Architecture connection-oriented protocol).<ref>{{Cite web \|last=stevewhims \|title=Remote Procedure Calls Using RPC over HTTP - Win32 apps \|url=https://docs.microsoft.com/en-us/windows/win32/rpc/remote-procedure-calls-using-rpc-over-http \|access-date=2022-08-03 \|website=docs.microsoft.com \|language=en-us}}</ref>		DCOM was a major competitor to [[CORBA]].<ref>{{Cite journal \|last=Nowak \|first=Filip \|last2=Qasim \|first2=Mohsin \|title=A Comparison of Distributed Object Technologies CORBA vs DCOM \|url=https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-url=https://web.archive.org/web/20170829054415/https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-date=2017-08-29 \|url-status=live \|journal=}}</ref> Proponents of both of these technologies saw them as one day becoming the model for code and service-reuse over the [[Internet]]. However, the difficulties involved in getting either of these technologies to work over Internet [[Firewall (networking)\|firewalls]], and on unknown and insecure machines, meant that normal [[HTTP]] requests in combination with [[web browser]]s won out over both of them.<ref>{{Cite web \|title=Object Technology Jeff Sutherland: Web Services: Better than CORBA or DCOM? \|url=http://jeffsutherland.com/2003/10/web-services-better-than-corba-or-dcom.html \|access-date=2022-08-03 \|language=en}}</ref> Microsoft, at one point, attempted to remediate these shortcomings by adding an extra HTTP transport to DCE/RPC called ''ncacn_http'' (Network Computing Architecture connection-oriented protocol).<ref>{{Cite web \|last=stevewhims \|title=Remote Procedure Calls Using RPC over HTTP - Win32 apps \|url=https://docs.microsoft.com/en-us/windows/win32/rpc/remote-procedure-calls-using-rpc-over-http \|access-date=2022-08-03 \|website=docs.microsoft.com \|language=en-us}}</ref>

	DCOM was publicly launched as a beta for Windows 95 September 18, 1996.<ref>[https://news.microsoft.com/1996/09/18/microsoft-releases-beta-version-of-dcom-for-windows-95/#Microsoft Press Release Announcing DCOM Beta]</ref>		DCOM was publicly launched as a beta for Windows 95 September 18, 1996.<ref>[https://news.microsoft.com/1996/09/18/microsoft-releases-beta-version-of-dcom-for-windows-95/#Microsoft Press Release Announcing DCOM Beta]</ref>

CoolieCoolster: Fixed typo (via WP:JWB)

2024-04-20T19:49:44Z

Fixed typo (via WP:JWB)

← Previous revision		Revision as of 19:49, 20 April 2024
Line 20:		Line 20:
	As part of the initiative that began at Microsoft as part of Secure Development Lifecycle to re-architect insecure code, DCOM saw some significant security-focused changes in Windows XP Service Pack 2.<ref>[https://technet.microsoft.com/en-us/library/bb457156.aspx#EIAA DCOM Security Enhancements]</ref>		As part of the initiative that began at Microsoft as part of Secure Development Lifecycle to re-architect insecure code, DCOM saw some significant security-focused changes in Windows XP Service Pack 2.<ref>[https://technet.microsoft.com/en-us/library/bb457156.aspx#EIAA DCOM Security Enhancements]</ref>

	In response to a security vulnerability reported by Tencent Security Xuanwu Lab in June of 2021,<ref>{{Cite web \|title=Security Update Guide - Microsoft Security Response Center \|url=https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-26414 \|access-date=2022-08-03 \|website=msrc.microsoft.com}}</ref> Microsoft released security updates for several versions of Windows and Windows Server, hardening access to DCOM.<ref>{{Cite web \|title=KB5004442—Manage changes for Windows DCOM Server Security Feature Bypass (CVE-2021-26414) \|url=https://support.microsoft.com/en-us/topic/kb5004442-manage-changes-for-windows-dcom-server-security-feature-bypass-cve-2021-26414-f1400b52-c141-43d2-941e-37ed901c769c \|access-date=2022-08-03 \|website=support.microsoft.com}}</ref>		In response to a security vulnerability reported by Tencent Security Xuanwu Lab in June 2021,<ref>{{Cite web \|title=Security Update Guide - Microsoft Security Response Center \|url=https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-26414 \|access-date=2022-08-03 \|website=msrc.microsoft.com}}</ref> Microsoft released security updates for several versions of Windows and Windows Server, hardening access to DCOM.<ref>{{Cite web \|title=KB5004442—Manage changes for Windows DCOM Server Security Feature Bypass (CVE-2021-26414) \|url=https://support.microsoft.com/en-us/topic/kb5004442-manage-changes-for-windows-dcom-server-security-feature-bypass-cve-2021-26414-f1400b52-c141-43d2-941e-37ed901c769c \|access-date=2022-08-03 \|website=support.microsoft.com}}</ref>

	== Alternative versions and implementations ==		== Alternative versions and implementations ==

Fathoms Below: Reverted edits by Hazzyedit (talk) to last revision by Frap: please use the talk page (WP:TPHELP) or be bold and fix the problem

2024-01-05T03:35:58Z

Reverted edits by Hazzyedit (talk) to last revision by Frap: please use the talk page (WP:TPHELP) or be bold and fix the problem

← Previous revision		Revision as of 03:35, 5 January 2024
Line 29:		Line 29:

	'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>		'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>

	DCOM popped up on my computer today.

	== See also ==		== See also ==

Hazzyedit at 03:35, 5 January 2024

2024-01-05T03:35:35Z

← Previous revision		Revision as of 03:35, 5 January 2024
Line 29:		Line 29:

	'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>		'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>

			DCOM popped up on my computer today.

	== See also ==		== See also ==

Frap: /* Security Improvements */ MOS:HEAD

2023-06-21T19:19:29Z

Security Improvements: MOS:HEAD

← Previous revision		Revision as of 19:19, 21 June 2023
Line 17:		Line 17:
	DCOM is supported natively in all versions of Windows starting from Windows 95, and all versions of Windows Server since Windows NT 4.0<ref>{{Cite web \|date=June 25, 2021 \|title=Distributed Component Object Model (DCOM) Remote Protocol \|url=https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-DCOM/%5bMS-DCOM%5d.pdf \|archive-url=https://web.archive.org/web/20210509140147/https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-DCOM/%5BMS-DCOM%5D.pdf \|archive-date=2021-05-09 \|url-status=live \|access-date=August 3, 2022 \|website=Microsoft - Distributed Component Object Model (DCOM) Remote Protocol}}</ref>		DCOM is supported natively in all versions of Windows starting from Windows 95, and all versions of Windows Server since Windows NT 4.0<ref>{{Cite web \|date=June 25, 2021 \|title=Distributed Component Object Model (DCOM) Remote Protocol \|url=https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-DCOM/%5bMS-DCOM%5d.pdf \|archive-url=https://web.archive.org/web/20210509140147/https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-DCOM/%5BMS-DCOM%5D.pdf \|archive-date=2021-05-09 \|url-status=live \|access-date=August 3, 2022 \|website=Microsoft - Distributed Component Object Model (DCOM) Remote Protocol}}</ref>

	== Security ~~Improvements~~ ==		== Security improvements ==
	As part of the initiative that began at Microsoft as part of Secure Development Lifecycle to re-architect insecure code, DCOM saw some significant security-focused changes in Windows XP Service Pack 2.<ref>[https://technet.microsoft.com/en-us/library/bb457156.aspx#EIAA DCOM Security Enhancements]</ref>		As part of the initiative that began at Microsoft as part of Secure Development Lifecycle to re-architect insecure code, DCOM saw some significant security-focused changes in Windows XP Service Pack 2.<ref>[https://technet.microsoft.com/en-us/library/bb457156.aspx#EIAA DCOM Security Enhancements]</ref>

Pmw2piVB: Rm live CS1 url status

2023-02-18T05:02:22Z

Rm live CS1 url status

← Previous revision		Revision as of 05:02, 18 February 2023
Line 23:		Line 23:

	== Alternative versions and implementations ==		== Alternative versions and implementations ==
	'''COMsource''' is a Unix based implementation of DCOM, allowing interoperability between different platforms. Its source code is available, along with full and complete documentation, sufficient to use and also implement an interoperable version of DCOM. COMsource comes directly from the [[Windows NT]] 4.0 source code, and includes the source code for a [[Windows Registry\|Windows NT Registry Service]]. <ref>{{Cite web \|title=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms \|url=http://www.opengroup.org/comsource/datasheet.htm ~~\|url-status=live~~ \|website=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms}}</ref>		'''COMsource''' is a Unix based implementation of DCOM, allowing interoperability between different platforms. Its source code is available, along with full and complete documentation, sufficient to use and also implement an interoperable version of DCOM. COMsource comes directly from the [[Windows NT]] 4.0 source code, and includes the source code for a [[Windows Registry\|Windows NT Registry Service]]. <ref>{{Cite web \|title=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms \|url=http://www.opengroup.org/comsource/datasheet.htm \|website=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms}}</ref>

	In 1995, Digital and [[Microsoft]] announced Affinity for OpenVMS (also known as NT Affinity) which was intended to allow OpenVMS to serve as the [[persistence layer]] for Windows NT [[Client–server model\|client-server applications]].<ref name="vms-20-years">{{cite web\|url=https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-url=https://web.archive.org/web/20210419084702/https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-date=2021-04-19 \|url-status=live\|date=October 1997\|title=OpenVMS at 20 Nothing stops it\|publisher=Digital\|access-date=2021-02-12}}</ref> As part of this initiative, an implementation of the Distributed Component Object Model (DCOM) was added to OpenVMS Alpha.<ref name="com-compaq">{{cite book\|title=COM Beyond Microsoft: Designing and Implementing COM Servers on Compaq Platforms\|url=https://books.google.com/books?id=i47yKPSDd1gC\|isbn=1555582265\|author=Gene Cronin, Terence P. Sherlock\|date=2000}}</ref> In order to support DCOM, VMS was provided with implementations of the Windows Registry, [[NTLM]] authentication, and a subset of [[Win32]] APIs needed to support COM.<ref>{{cite web\|url=http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|title=OpenVMS Connectivity Developer Guide		In 1995, Digital and [[Microsoft]] announced Affinity for OpenVMS (also known as NT Affinity) which was intended to allow OpenVMS to serve as the [[persistence layer]] for Windows NT [[Client–server model\|client-server applications]].<ref name="vms-20-years">{{cite web\|url=https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-url=https://web.archive.org/web/20210419084702/https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-date=2021-04-19 \|url-status=live\|date=October 1997\|title=OpenVMS at 20 Nothing stops it\|publisher=Digital\|access-date=2021-02-12}}</ref> As part of this initiative, an implementation of the Distributed Component Object Model (DCOM) was added to OpenVMS Alpha.<ref name="com-compaq">{{cite book\|title=COM Beyond Microsoft: Designing and Implementing COM Servers on Compaq Platforms\|url=https://books.google.com/books?id=i47yKPSDd1gC\|isbn=1555582265\|author=Gene Cronin, Terence P. Sherlock\|date=2000}}</ref> In order to support DCOM, VMS was provided with implementations of the Windows Registry, [[NTLM]] authentication, and a subset of [[Win32]] APIs needed to support COM.<ref>{{cite web\|url=http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|title=OpenVMS Connectivity Developer Guide

← Previous revision		Revision as of 03:29, 22 April 2025
Line 1:		Line 1:
	{{Short description\|Software for communication between software components}}		{{Short description\|Software for communication between software components}}

	~~{{Redirect\|Dcom\|the doctoral degree\|Doctor of Commerce\|other uses\|DCOM (disambiguation)}}~~'''Distributed Component Object Model''' ('''DCOM''') is a [[proprietary software\|proprietary]] [[Microsoft]] technology for communication between [[software componentry\|software components]] on networked [[computer]]s. DCOM, which originally was called "Network [[Object Linking and Embedding\|OLE]]", extends Microsoft's [[Component Object Model\|COM]], and provides the communication substrate under Microsoft's [[Component Object Model#COM+\|COM+]] application server infrastructure.		'''Distributed Component Object Model''' ('''DCOM''') is a [[proprietary software\|proprietary]] [[Microsoft]] technology for communication between [[software componentry\|software components]] on networked [[computer]]s. DCOM, which originally was called "Network [[Object Linking and Embedding\|OLE]]", extends Microsoft's [[Component Object Model\|COM]], and provides the communication substrate under Microsoft's [[Component Object Model#COM+\|COM+]] application server infrastructure.

	The extension COM into Distributed COM was due to extensive use of [[DCE/RPC]] (Distributed Computing Environment/Remote Procedure Calls) – more specifically Microsoft's enhanced version, known as [[MSRPC]]. <ref>{{Cite web \|title=What is Distributed Component Object Model (DCOM)? \|url=https://www.techtarget.com/whatis/definition/DCOM-Distributed-Component-Object-Model \|access-date=2022-08-03 \|website=WhatIs.com \|language=en}}</ref>		The extension COM into Distributed COM was due to extensive use of [[DCE/RPC]] (Distributed Computing Environment/Remote Procedure Calls) – more specifically Microsoft's enhanced version, known as [[MSRPC]]. <ref>{{Cite web \|title=What is Distributed Component Object Model (DCOM)? \|url=https://www.techtarget.com/whatis/definition/DCOM-Distributed-Component-Object-Model \|access-date=2022-08-03 \|website=WhatIs.com \|language=en}}</ref>

← Previous revision		Revision as of 17:04, 20 November 2024
Line 11:		Line 11:
	One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who is responsible for freeing memory.<ref>{{Cite web \|title=DCE 1.1: Remote Procedure Call - Introduction to the RPC API \|url=https://pubs.opengroup.org/onlinepubs/9629399/chap2.htm \|access-date=2022-08-03 \|website=pubs.opengroup.org}}</ref>		One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who is responsible for freeing memory.<ref>{{Cite web \|title=DCE 1.1: Remote Procedure Call - Introduction to the RPC API \|url=https://pubs.opengroup.org/onlinepubs/9629399/chap2.htm \|access-date=2022-08-03 \|website=pubs.opengroup.org}}</ref>

	DCOM was a major competitor to [[CORBA]].<ref>{{Cite journal \|~~last~~=Nowak \|~~first~~=Filip \|last2=Qasim \|first2=Mohsin \|title=A Comparison of Distributed Object Technologies CORBA vs DCOM \|url=https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-url=https://web.archive.org/web/20170829054415/https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-date=2017-08-29 \|url-status=live \|journal=}}</ref> Proponents of both of these technologies saw them as one day becoming the model for code and service-reuse over the [[Internet]]. However, the difficulties involved in getting either of these technologies to work over Internet [[Firewall (networking)\|firewalls]], and on unknown and insecure machines, meant that normal [[HTTP]] requests in combination with [[web browser]]s won out over both of them.<ref>{{Cite web \|title=Object Technology Jeff Sutherland: Web Services: Better than CORBA or DCOM? \|url=http://jeffsutherland.com/2003/10/web-services-better-than-corba-or-dcom.html \|access-date=2022-08-03 \|language=en}}</ref> Microsoft, at one point, attempted to remediate these shortcomings by adding an extra HTTP transport to DCE/RPC called ''ncacn_http'' (Network Computing Architecture connection-oriented protocol).<ref>{{Cite web \|last=stevewhims \|title=Remote Procedure Calls Using RPC over HTTP - Win32 apps \|url=https://docs.microsoft.com/en-us/windows/win32/rpc/remote-procedure-calls-using-rpc-over-http \|access-date=2022-08-03 \|website=docs.microsoft.com \|language=en-us}}</ref>		DCOM was a major competitor to [[CORBA]].<ref>{{Cite journal \|last1=Nowak \|first1=Filip \|last2=Qasim \|first2=Mohsin \|title=A Comparison of Distributed Object Technologies CORBA vs DCOM \|url=https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-url=https://web.archive.org/web/20170829054415/https://middlewares.files.wordpress.com/2008/04/dcom_corba.pdf \|archive-date=2017-08-29 \|url-status=live \|journal=}}</ref> Proponents of both of these technologies saw them as one day becoming the model for code and service-reuse over the [[Internet]]. However, the difficulties involved in getting either of these technologies to work over Internet [[Firewall (networking)\|firewalls]], and on unknown and insecure machines, meant that normal [[HTTP]] requests in combination with [[web browser]]s won out over both of them.<ref>{{Cite web \|title=Object Technology Jeff Sutherland: Web Services: Better than CORBA or DCOM? \|url=http://jeffsutherland.com/2003/10/web-services-better-than-corba-or-dcom.html \|access-date=2022-08-03 \|language=en}}</ref> Microsoft, at one point, attempted to remediate these shortcomings by adding an extra HTTP transport to DCE/RPC called ''ncacn_http'' (Network Computing Architecture connection-oriented protocol).<ref>{{Cite web \|last=stevewhims \|title=Remote Procedure Calls Using RPC over HTTP - Win32 apps \|url=https://docs.microsoft.com/en-us/windows/win32/rpc/remote-procedure-calls-using-rpc-over-http \|access-date=2022-08-03 \|website=docs.microsoft.com \|date=23 August 2019 \|language=en-us}}</ref>

	DCOM was publicly launched as a beta for Windows 95 September 18, 1996.<ref>[https://news.microsoft.com/1996/09/18/microsoft-releases-beta-version-of-dcom-for-windows-95/#Microsoft Press Release Announcing DCOM Beta]</ref>		DCOM was publicly launched as a beta for Windows 95 September 18, 1996.<ref>[https://news.microsoft.com/1996/09/18/microsoft-releases-beta-version-of-dcom-for-windows-95/#Microsoft Press Release Announcing DCOM Beta]</ref>
Line 25:		Line 25:
	'''COMsource''' is a Unix based implementation of DCOM, allowing interoperability between different platforms. Its source code is available, along with full and complete documentation, sufficient to use and also implement an interoperable version of DCOM. COMsource comes directly from the [[Windows NT]] 4.0 source code, and includes the source code for a [[Windows Registry\|Windows NT Registry Service]]. <ref>{{Cite web \|title=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms \|url=http://www.opengroup.org/comsource/datasheet.htm \|website=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms}}</ref>		'''COMsource''' is a Unix based implementation of DCOM, allowing interoperability between different platforms. Its source code is available, along with full and complete documentation, sufficient to use and also implement an interoperable version of DCOM. COMsource comes directly from the [[Windows NT]] 4.0 source code, and includes the source code for a [[Windows Registry\|Windows NT Registry Service]]. <ref>{{Cite web \|title=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms \|url=http://www.opengroup.org/comsource/datasheet.htm \|website=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms}}</ref>

	In 1995, Digital and [[Microsoft]] announced Affinity for OpenVMS (also known as NT Affinity) which was intended to allow OpenVMS to serve as the [[persistence layer]] for Windows NT [[Client–server model\|client-server applications]].<ref name="vms-20-years">{{cite web\|url=https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-url=https://web.archive.org/web/20210419084702/https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-date=2021-04-19 \|url-status=live\|date=October 1997\|title=OpenVMS at 20 Nothing stops it\|publisher=Digital\|access-date=2021-02-12}}</ref> As part of this initiative, an implementation of the Distributed Component Object Model (DCOM) was added to OpenVMS Alpha.<ref name="com-compaq">{{cite book\|title=COM Beyond Microsoft: Designing and Implementing COM Servers on Compaq Platforms\|url=https://books.google.com/books?id=i47yKPSDd1gC\|isbn=1555582265\|author=Gene Cronin, Terence P. Sherlock\|date=2000}}</ref> In order to support DCOM, VMS was provided with implementations of the Windows Registry, [[NTLM]] authentication, and a subset of [[Win32]] APIs needed to support COM.<ref>{{cite web\|url=http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|title=OpenVMS Connectivity Developer Guide\|date=July 2000\|access-date=2021-01-01\|website=hpe.com\|archive-date=2020-12-04\|archive-url=https://web.archive.org/web/20201204205526/http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|url-status=dead}}</ref> DCOM was first added to OpenVMS V7.2-1 for the Alpha.<ref>{{cite web\|url=http://odl.sysworks.biz/disk$vaxdocmar002/opsys/vmsos721/6614/6614pro_contents.html\|title=OpenVMS Alpha V7.2-1 Release Notes\|website=odl.sysworks.biz\|access-date=2021-01-01\|date=January 1999}}</ref> A similar implementation of DCOM was added to [[Digital Unix]] as part of the AllConnect program.<ref name="com-compaq" />		In 1995, Digital and [[Microsoft]] announced Affinity for OpenVMS (also known as NT Affinity) which was intended to allow OpenVMS to serve as the [[persistence layer]] for Windows NT [[Client–server model\|client-server applications]].<ref name="vms-20-years">{{cite web\|url=https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-url=https://web.archive.org/web/20210419084702/https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-date=2021-04-19 \|url-status=live\|date=October 1997\|title=OpenVMS at 20 Nothing stops it\|publisher=Digital\|access-date=2021-02-12}}</ref> As part of this initiative, an implementation of the Distributed Component Object Model (DCOM) was added to OpenVMS Alpha.<ref name="com-compaq">{{cite book\|title=COM Beyond Microsoft: Designing and Implementing COM Servers on Compaq Platforms\|url=https://books.google.com/books?id=i47yKPSDd1gC\|isbn=1555582265\|author=Gene Cronin, Terence P. Sherlock\|date=2000\| publisher=Digital Press }}</ref> In order to support DCOM, VMS was provided with implementations of the Windows Registry, [[NTLM]] authentication, and a subset of [[Win32]] APIs needed to support COM.<ref>{{cite web\|url=http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|title=OpenVMS Connectivity Developer Guide\|date=July 2000\|access-date=2021-01-01\|website=hpe.com\|archive-date=2020-12-04\|archive-url=https://web.archive.org/web/20201204205526/http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|url-status=dead}}</ref> DCOM was first added to OpenVMS V7.2-1 for the Alpha.<ref>{{cite web\|url=http://odl.sysworks.biz/disk$vaxdocmar002/opsys/vmsos721/6614/6614pro_contents.html\|title=OpenVMS Alpha V7.2-1 Release Notes\|website=odl.sysworks.biz\|access-date=2021-01-01\|date=January 1999}}</ref> A similar implementation of DCOM was added to [[Digital Unix]] as part of the AllConnect program.<ref name="com-compaq" />

	'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>		'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>

← Previous revision		Revision as of 15:40, 19 November 2024
Line 25:		Line 25:
	'''COMsource''' is a Unix based implementation of DCOM, allowing interoperability between different platforms. Its source code is available, along with full and complete documentation, sufficient to use and also implement an interoperable version of DCOM. COMsource comes directly from the [[Windows NT]] 4.0 source code, and includes the source code for a [[Windows Registry\|Windows NT Registry Service]]. <ref>{{Cite web \|title=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms \|url=http://www.opengroup.org/comsource/datasheet.htm \|website=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms}}</ref>		'''COMsource''' is a Unix based implementation of DCOM, allowing interoperability between different platforms. Its source code is available, along with full and complete documentation, sufficient to use and also implement an interoperable version of DCOM. COMsource comes directly from the [[Windows NT]] 4.0 source code, and includes the source code for a [[Windows Registry\|Windows NT Registry Service]]. <ref>{{Cite web \|title=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms \|url=http://www.opengroup.org/comsource/datasheet.htm \|website=DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms}}</ref>

	In 1995, Digital and [[Microsoft]] announced Affinity for OpenVMS (also known as NT Affinity) which was intended to allow OpenVMS to serve as the [[persistence layer]] for Windows NT [[Client–server model\|client-server applications]].<ref name="vms-20-years">{{cite web\|url=https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-url=https://web.archive.org/web/20210419084702/https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-date=2021-04-19 \|url-status=live\|date=October 1997\|title=OpenVMS at 20 Nothing stops it\|publisher=Digital\|access-date=2021-02-12}}</ref> As part of this initiative, an implementation of the Distributed Component Object Model (DCOM) was added to OpenVMS Alpha.<ref name="com-compaq">{{cite book\|title=COM Beyond Microsoft: Designing and Implementing COM Servers on Compaq Platforms\|url=https://books.google.com/books?id=i47yKPSDd1gC\|isbn=1555582265\|author=Gene Cronin, Terence P. Sherlock\|date=2000}}</ref> In order to support DCOM, VMS was provided with implementations of the Windows Registry, [[NTLM]] authentication, and a subset of [[Win32]] APIs needed to support COM.<ref>{{cite web\|url=http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|title=OpenVMS Connectivity Developer Guide		In 1995, Digital and [[Microsoft]] announced Affinity for OpenVMS (also known as NT Affinity) which was intended to allow OpenVMS to serve as the [[persistence layer]] for Windows NT [[Client–server model\|client-server applications]].<ref name="vms-20-years">{{cite web\|url=https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-url=https://web.archive.org/web/20210419084702/https://h50146.www5.hpe.com/products/software/oe/openvms/history/vaxvms20/pdf/vmsbook.pdf \|archive-date=2021-04-19 \|url-status=live\|date=October 1997\|title=OpenVMS at 20 Nothing stops it\|publisher=Digital\|access-date=2021-02-12}}</ref> As part of this initiative, an implementation of the Distributed Component Object Model (DCOM) was added to OpenVMS Alpha.<ref name="com-compaq">{{cite book\|title=COM Beyond Microsoft: Designing and Implementing COM Servers on Compaq Platforms\|url=https://books.google.com/books?id=i47yKPSDd1gC\|isbn=1555582265\|author=Gene Cronin, Terence P. Sherlock\|date=2000}}</ref> In order to support DCOM, VMS was provided with implementations of the Windows Registry, [[NTLM]] authentication, and a subset of [[Win32]] APIs needed to support COM.<ref>{{cite web\|url=http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|title=OpenVMS Connectivity Developer Guide\|date=July 2000\|access-date=2021-01-01\|website=hpe.com\|archive-date=2020-12-04\|archive-url=https://web.archive.org/web/20201204205526/http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6539/6539pro.html\|url-status=dead}}</ref> DCOM was first added to OpenVMS V7.2-1 for the Alpha.<ref>{{cite web\|url=http://odl.sysworks.biz/disk$vaxdocmar002/opsys/vmsos721/6614/6614pro_contents.html\|title=OpenVMS Alpha V7.2-1 Release Notes\|website=odl.sysworks.biz\|access-date=2021-01-01\|date=January 1999}}</ref> A similar implementation of DCOM was added to [[Digital Unix]] as part of the AllConnect program.<ref name="com-compaq" />
	\|date=July 2000\|access-date=2021-01-01\|website=hpe.com}}</ref> DCOM was first added to OpenVMS V7.2-1 for the Alpha.<ref>{{cite web\|url=http://odl.sysworks.biz/disk$vaxdocmar002/opsys/vmsos721/6614/6614pro_contents.html\|title=OpenVMS Alpha V7.2-1 Release Notes\|website=odl.sysworks.biz\|access-date=2021-01-01\|date=January 1999}}</ref> A similar implementation of DCOM was added to [[Digital Unix]] as part of the AllConnect program.<ref name="com-compaq" />

	'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>		'''TangramCOM''' was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.<ref>{{Cite web \|title=Home - TangramCOM \|url=http://www.andjoin.com/Home \|access-date=2022-08-03 \|website=www.andjoin.com}}</ref>