DCERouter - Revision history

Foxi352: /* Programmer's Guide */

2012-07-13T12:57:19Z

Programmer's Guide

←Older revision		Revision as of 12:57, 13 July 2012
Line 27:		Line 27:
	Messages can be sent on the commandline to the DCERouter (and thereby to devices) using the [[MessageSend]] utility.		Messages can be sent on the commandline to the DCERouter (and thereby to devices) using the [[MessageSend]] utility.

	DCERouter listens on port 3450 per default.		DCERouter listens on port 3450 per default. Recent 10.04 build also listen on ipv6, same port.

Marie.o: Added note about port 3450

2008-10-13T17:03:42Z

Added note about port 3450

←Older revision		Revision as of 17:03, 13 October 2008
Line 26:		Line 26:

	Messages can be sent on the commandline to the DCERouter (and thereby to devices) using the [[MessageSend]] utility.		Messages can be sent on the commandline to the DCERouter (and thereby to devices) using the [[MessageSend]] utility.

			DCERouter listens on port 3450 per default.

Perspectoff at 00:14, 20 May 2008

2008-05-20T00:14:38Z

←Older revision		Revision as of 00:14, 20 May 2008
Line 1:		Line 1:
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]

	DCERouter has no options or user interface, so there is no documentation for users--only technical documentation.		DCERouter has no options or user interface, so there is no documentation for users -- only technical documentation.

	DCERouter is the central piece of software ~~that all~~ [[LinuxMCE DCE Devices]] for documentation on the DCE socket-based messaging protocol		DCERouter is the central piece of software. See [[LinuxMCE DCE Devices]] for documentation on the DCE socket-based messaging protocol.

	Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer ~~with~~ an ~~internet~~ connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins~~. However~~, they are ~~really~~ identical to ~~the~~ other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. ~~Of course, running~~ as a plug-in is ~~much~~ more dangerous since it is in the same memory space and can therefore crash the whole router, ~~and bring~~ the whole LinuxMCE system down. Therefore it is ~~encourages~~ to run devices as plug-ins only when necessary ~~because~~ the device needs to be able to intercept messages that may not be directed to it. Since all ~~the~~ plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.		Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or on another computer that is connected by an Ethernet connection.

			A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins, but they are identical to other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles -- one to run as a normal, external DCE Device, and one to run as a plug-in. Running as a plug-in is more dangerous since it is in the same memory space and can therefore crash the whole router, potentially bringing the whole LinuxMCE system down. Therefore it is encouraged to run devices as plug-ins only when necessary, such as when the device needs to be able to intercept messages that may not be directed to it.

			Since all plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the "so" (for "shared object") switch on the Makefile under Linux.

	=Programmer's Guide=		=Programmer's Guide=

Matthew: Use MessageSend

2008-01-22T00:27:11Z

Use MessageSend

←Older revision		Revision as of 00:27, 22 January 2008
Line 6:		Line 6:

	Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.		Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.

	=Programmer's Guide=		=Programmer's Guide=

Line 19:		Line 20:
	-f base path -- device requests for files will be relative to this path		-f base path -- device requests for files will be relative to this path
	-l logger -- where to put the log</pre>		-l logger -- where to put the log</pre>

			Messages can be sent on the commandline to the DCERouter (and thereby to devices) using the [[MessageSend]] utility.

Matthew: Shift section degrees down to start at 1

2008-01-22T00:25:54Z

Shift section degrees down to start at 1

←Older revision		Revision as of 00:25, 22 January 2008
Line 6:		Line 6:

	Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.		Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.
	==Programmer's Guide==		=Programmer's Guide=

	<pre>Router, v.2.0.0.44.0709022200		<pre>Router, v.2.0.0.44.0709022200

Rwilson131: added Help Output

2007-12-07T04:58:31Z

added Help Output

@@ Line 1: / Line 1: @@
 [[Category: Programmer's Guide]]
-<p>DCERouter has no options or user interface, so there is no documentation for users--only technical documentation.</p>
+DCERouter has no options or user interface, so there is no documentation for users--only technical documentation.
-<p>DCERouter is the central piece of software that all [[LinuxMCE DCE Devices]] for documentation on the DCE socket-based messaging protocol.</p>
-<p>Normally DCE Devices run separately from the router.  Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection.  A DCE Device can also be run in the DCE Router's memory space.  These devices are called plug-ins.  However, they are really identical to the other DCE Devices.  In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in.  Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down.  Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it.  Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions.  To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site.  Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.</p>
+DCERouter is the central piece of software that all [[LinuxMCE DCE Devices]] for documentation on the DCE socket-based messaging protocol

Rwilson131: DCE Router moved to DCERouter

2007-09-21T02:56:41Z

DCE Router moved to DCERouter

←Older revision	Revision as of 02:56, 21 September 2007
(No difference)

Mstovenour: Added to Category: Programmer's Guide

2007-08-11T14:39:14Z

Added to Category: Programmer's Guide

←Older revision		Revision as of 14:39, 11 August 2007
Line 1:		Line 1:
			[[Category: Programmer's Guide]]

	<p>DCERouter has no options or user interface, so there is no documentation for users--only technical documentation.</p>		<p>DCERouter has no options or user interface, so there is no documentation for users--only technical documentation.</p>
	<p>DCERouter is the central piece of software that all [[LinuxMCE DCE Devices]] for documentation on the DCE socket-based messaging protocol.</p>		<p>DCERouter is the central piece of software that all [[LinuxMCE DCE Devices]] for documentation on the DCE socket-based messaging protocol.</p>
	<p>Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.</p>		<p>Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.</p>

Jerry finn at 16:12, 16 March 2007

2007-03-16T16:12:28Z

←Older revision		Revision as of 16:12, 16 March 2007
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table><p>DCERouter has no options or user interface, so there is no documentation for users--only technical documentation.</p>		<p>DCERouter has no options or user interface, so there is no documentation for users--only technical documentation.</p>
	<p>DCERouter is the central piece of software that all [[~~Pluto~~ DCE Devices]] for documentation on the DCE socket-based messaging protocol.</p>		<p>DCERouter is the central piece of software that all [[LinuxMCE DCE Devices]] for documentation on the DCE socket-based messaging protocol.</p>
	<p>Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.</p>		<p>Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.</p>

Jerry finn at 09:57, 15 March 2007

2007-03-15T09:57:28Z

←Older revision		Revision as of 09:57, 15 March 2007
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table><p>DCERouter has no options or user interface, so there is no documentation for users--only technical documentation.</p>		<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table><p>DCERouter has no options or user interface, so there is no documentation for users--only technical documentation.</p>
	<p>DCERouter is the central piece of software that all [[Pluto DCE Devices]] for documentation on the DCE socket-based messaging protocol.</p>		<p>DCERouter is the central piece of software that all [[Pluto DCE Devices]] for documentation on the DCE socket-based messaging protocol.</p>
	<p>Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole ~~Pluto~~ system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.</p>		<p>Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.</p>