DCOP - Revision history

Blu256: Moved categories to bottom and removed empty space

2022-04-21T15:31:42Z

Moved categories to bottom and removed empty space

Blu256: -Applicable to TDE (redundant)

2022-04-21T15:30:48Z

-Applicable to TDE (redundant)

Blu256: /* Tutorials */ Replace IBM tutorial link with archived link

2022-01-30T17:00:28Z

Tutorials: Replace IBM tutorial link with archived link

Blu256: Blu256 moved page DCOP (KDE3 Architecture) to DCOP: Probably a better title (redirect left in place)

2022-01-21T12:07:25Z

Blu256 moved page DCOP (KDE3 Architecture) to DCOP: Probably a better title (redirect left in place)

Blu256: /* External links */ Reinserted link to IBM tutorial since an archive link has been found

2022-01-21T11:47:12Z

External links: Reinserted link to IBM tutorial since an archive link has been found

Blu256: Added links with more information about DCOP

2022-01-18T13:37:22Z

Added links with more information about DCOP

Blu256: Qt→TQt

2021-08-25T18:23:10Z

Qt→TQt

Blu256: Added picture, minor text improvements

2021-08-22T19:55:06Z

Added picture, minor text improvements

Blu256: Bold

2021-08-22T19:51:22Z

Bold

Blu256: Updated API doc. link, commented out dead link, added {{Applicable to TDE}} and beadings

2021-08-22T19:51:00Z

Updated API doc. link, commented out dead link, added {{Applicable to TDE}} and beadings

@@ Line 1: / Line 1: @@
-[[Category:KDE3]]
-[[Category:Architecture]]
-[[Category:Developers]]
 [[File:Servicemenus kdcop.png|thumb|KDCOP is a graphical DCOP browser/client.]]
@@ Line 26: / Line 22: @@
 * [http://web.archive.org/web/20100126055754/http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.html Creating a DCOP Interface]
 * [http://web.archive.org/web/20070204134744/http://www-128.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP] (there are links to even more DCOP tutorials in the bottom of this page)
+[[Category:KDE3]]
+[[Category:Architecture]]
+[[Category:Developers]]

@@ Line 2: / Line 2: @@
 [[Category:Architecture]]
 [[Category:Developers]]
-{{Applicable to TDE}}
 [[File:Servicemenus kdcop.png|thumb|KDCOP is a graphical DCOP browser/client.]]

@@ Line 26: / Line 26: @@
 == Tutorials ==
 * [http://web.archive.org/web/20100126055754/http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.html Creating a DCOP Interface]
-* [http://www-128.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP] (there are links to even more DCOP tutorials in the bottom of this page)
+* [http://web.archive.org/web/20070204134744/http://www-128.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP] (there are links to even more DCOP tutorials in the bottom of this page)

@@ Line 20: / Line 20: @@
 See the following resources for further information:
+== API documentation ==
 * [http://trinitydesktop.org/docs/trinity/tdelibs/dcop/html/ Long description of DCOP with examples in the official API documentation]
 * [http://trinitydesktop.org/docs/trinity/tdelibs/dcop/html/annotated.html A list of DCOP classes in the official API documentation]
+== Tutorials ==
 * [http://web.archive.org/web/20100126055754/http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.html Creating a DCOP Interface]
-<!-- * [http://www-106.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP] (dead link, no Wayback)
+* [http://www-128.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP] (there are links to even more DCOP tutorials in the bottom of this page)

@@ Line 18: / Line 18: @@
 = External links =
-See the following tutorials for further information:
+See the following resources for further information:
+* [http://trinitydesktop.org/docs/trinity/tdelibs/dcop/html/ Long description of DCOP with examples in the official API documentation]
+* [http://trinitydesktop.org/docs/trinity/tdelibs/dcop/html/annotated.html A list of DCOP classes in the official API documentation]
 * [http://web.archive.org/web/20100126055754/http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.html Creating a DCOP Interface]
 <!-- * [http://www-106.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP] (dead link, no Wayback)

@@ Line 14: / Line 14: @@
 Two types of actions are possible with DCOP: ''"send and forget"'' messages, which do not block, and ''"calls"'', which block waiting for some data to be returned.
-Any data that will be sent is serialized (marshaled, for you CORBA fellows) using the built-in [http://trinitydesktop.org/docs/qt3/ntqdatastream.html QDataStream] operators available in all of the Qt classes. This is fast and easy. In fact it's so little work that you can easily write the marshaling code by hand. In addition, there's a simple IDL-like compiler available (dcopidl and dcopidl2cpp) that generates stubs and skeletons for you. Using the dcopidl compiler has the additional benefit of type safety.
+Any data that will be sent is serialized (marshaled, for you CORBA fellows) using the built-in [http://trinitydesktop.org/docs/qt3/ntqdatastream.html TQDataStream] operators available in all of the TQt classes. This is fast and easy. In fact it's so little work that you can easily write the marshaling code by hand. In addition, there's a simple IDL-like compiler available (dcopidl and dcopidl2cpp) that generates stubs and skeletons for you. Using the dcopidl compiler has the additional benefit of type safety.
 = External links =

@@ Line 4: / Line 4: @@
 {{Applicable to TDE}}
+[[File:Servicemenus kdcop.png|thumb|KDCOP is a graphical DCOP browser/client.]]
-'''DCOP''' is a simple IPC/RPC mechanism built to operate over sockets. Either unix domain sockets or tcp/ip sockets are supported. DCOP is built on top of the Inter Client Exchange (ICE) protocol, which comes standard as a part of X11R6 and later. It also depends on Qt, but beyond that it does not require any other libraries. Because of this, it is extremely lightweight, enabling it to be linked into all KDE applications with low overhead.
+'''DCOP''' is a simple IPC/RPC mechanism built to operate over sockets. Either Unix domain sockets or TCP/IP sockets are supported. DCOP is built on top of the Inter Client Exchange (ICE) protocol, which comes standard as a part of X11R6 and later. It also depends on TQt, but beyond that it does not require any other libraries. Because of this, it is extremely lightweight, enabling it to be linked into all TDE applications with low overhead.
 = How DCOP works =
@@ Line 11: / Line 12: @@
 The model is simple. Each application using DCOP is a client. They communicate to each other through a DCOP server, which functions like a traffic director, dispatching messages/calls to the proper destinations. All clients are peers of each other.
-Two types of actions are possible with DCOP: "send and forget" messages, which do not block, and "calls," which block waiting for some data to be returned.
+Two types of actions are possible with DCOP: ''"send and forget"'' messages, which do not block, and ''"calls"'', which block waiting for some data to be returned.
 Any data that will be sent is serialized (marshaled, for you CORBA fellows) using the built-in [http://trinitydesktop.org/docs/qt3/ntqdatastream.html QDataStream] operators available in all of the Qt classes. This is fast and easy. In fact it's so little work that you can easily write the marshaling code by hand. In addition, there's a simple IDL-like compiler available (dcopidl and dcopidl2cpp) that generates stubs and skeletons for you. Using the dcopidl compiler has the additional benefit of type safety.

← Older revision		Revision as of 19:51, 22 August 2021
Line 5:		Line 5:


	DCOP is a simple IPC/RPC mechanism built to operate over sockets. Either unix domain sockets or tcp/ip sockets are supported. DCOP is built on top of the Inter Client Exchange (ICE) protocol, which comes standard as a part of X11R6 and later. It also depends on Qt, but beyond that it does not require any other libraries. Because of this, it is extremely lightweight, enabling it to be linked into all KDE applications with low overhead.		'''DCOP''' is a simple IPC/RPC mechanism built to operate over sockets. Either unix domain sockets or tcp/ip sockets are supported. DCOP is built on top of the Inter Client Exchange (ICE) protocol, which comes standard as a part of X11R6 and later. It also depends on Qt, but beyond that it does not require any other libraries. Because of this, it is extremely lightweight, enabling it to be linked into all KDE applications with low overhead.

	= How DCOP works =		= How DCOP works =