Studio:Transport Server Component - Revision history

Timd: Text replace - 'Category:Reference' to 'Category:Studio:Reference'

2009-08-21T15:56:16Z

Text replace - 'Category:Reference' to 'Category:Studio:Reference'

← Older revision		Revision as of 15:56, 21 August 2009
Line 466:		Line 466:
	\|}		\|}
	[[Category:Studio]]		[[Category:Studio]]
	[[Category:Reference]]		[[Category:Studio:Reference]]

Timd: Transport Server Component moved to Studio:Transport Server Component

2009-08-18T21:29:08Z

Transport Server Component moved to Studio:Transport Server Component

← Older revision	Revision as of 21:29, 18 August 2009
(No difference)

Marku: /* transport.Connection.Transports.Properties.Item */

2009-06-11T21:56:26Z

transport.Connection.Transports.Properties.Item

← Older revision		Revision as of 21:56, 11 June 2009
Line 465:		Line 465:
	\| The value of the property. When set, the validation method of the transport will be called. Any failures in validation will be returned as exceptions here.		\| The value of the property. When set, the validation method of the transport will be called. Any failures in validation will be returned as exceptions here.
	\|}		\|}
			[[Category:Studio]]
	[[Category:Reference]]		[[Category:Reference]]

Ivailop: /* The Transport Server */

2009-06-05T00:37:18Z

The Transport Server

← Older revision		Revision as of 00:37, 5 June 2009
Line 17:		Line 17:
	To access the transport server, a client first registers with to it using a process id (PID). This is done transparently for script clients using the script wrapper named '''STRIDE.transport'''. In JScript getting ahold of the transport server may be done as follows:		To access the transport server, a client first registers with to it using a process id (PID). This is done transparently for script clients using the script wrapper named '''STRIDE.transport'''. In JScript getting ahold of the transport server may be done as follows:

	<source lang="~~jscript~~">		<source lang="javascript">
	var tpserver = new ActiveXObject("STRIDE.transport");		var tpserver = new ActiveXObject("STRIDE.transport");
	</source>		</source>

Ivailop: /* The Transport Server */

2009-06-05T00:37:01Z

The Transport Server

← Older revision		Revision as of 00:37, 5 June 2009
Line 17:		Line 17:
	To access the transport server, a client first registers with to it using a process id (PID). This is done transparently for script clients using the script wrapper named '''STRIDE.transport'''. In JScript getting ahold of the transport server may be done as follows:		To access the transport server, a client first registers with to it using a process id (PID). This is done transparently for script clients using the script wrapper named '''STRIDE.transport'''. In JScript getting ahold of the transport server may be done as follows:

	<source lang="~~perl~~">		<source lang="jscript">
	var tpserver = new ActiveXObject("STRIDE.transport");		var tpserver = new ActiveXObject("STRIDE.transport");
	</source>		</source>

Ivailop: /* The Transport Server */

2009-06-05T00:36:32Z

The Transport Server

← Older revision		Revision as of 00:36, 5 June 2009
Line 17:		Line 17:
	To access the transport server, a client first registers with to it using a process id (PID). This is done transparently for script clients using the script wrapper named '''STRIDE.transport'''. In JScript getting ahold of the transport server may be done as follows:		To access the transport server, a client first registers with to it using a process id (PID). This is done transparently for script clients using the script wrapper named '''STRIDE.transport'''. In JScript getting ahold of the transport server may be done as follows:

	<source ~~code~~="perl">		<source lang="perl">
	var tpserver = new ActiveXObject("STRIDE.transport");		var tpserver = new ActiveXObject("STRIDE.transport");
	</source>		</source>

Ivailop: /* The Transport Server */

2009-06-05T00:36:13Z

The Transport Server

← Older revision		Revision as of 00:36, 5 June 2009
Line 17:		Line 17:
	To access the transport server, a client first registers with to it using a process id (PID). This is done transparently for script clients using the script wrapper named '''STRIDE.transport'''. In JScript getting ahold of the transport server may be done as follows:		To access the transport server, a client first registers with to it using a process id (PID). This is done transparently for script clients using the script wrapper named '''STRIDE.transport'''. In JScript getting ahold of the transport server may be done as follows:

			<source code="perl">
	var tpserver = new ActiveXObject("STRIDE.transport");		var tpserver = new ActiveXObject("STRIDE.transport");
			</source>

	== Transport Server API ==		== Transport Server API ==

Ivailop: /* The Transport Server */

2009-06-05T00:35:37Z

The Transport Server

← Older revision		Revision as of 00:35, 5 June 2009
Line 13:		Line 13:
	== The Transport Server ==		== The Transport Server ==

	The Transport Server fields client requests to a target. The client communicates to the Transport Server. The Transport Server communicates to the target runtime of a target.		The Transport Server is an out-of-process COM server that fields client requests to a target and provides connection management, loopback and diagnostic features. The client communicates to the Transport Server. The Transport Server communicates to the target runtime of a target.

	To access the transport server, a client first registers with to it using a process id (PID). This is done transparently for script clients using the script wrapper named '''STRIDE.transport'''. In JScript getting ahold of the transport server may be done as follows:		To access the transport server, a client first registers with to it using a process id (PID). This is done transparently for script clients using the script wrapper named '''STRIDE.transport'''. In JScript getting ahold of the transport server may be done as follows:

Ivailop: /* The Host Transport Services */

2009-06-05T00:34:02Z

The Host Transport Services

← Older revision		Revision as of 00:34, 5 June 2009
Line 9:		Line 9:
	The Host Transport Services are defined in "transport.h" and each Transport DLL must implement the interfaces derived from the IStrideTransport class.		The Host Transport Services are defined in "transport.h" and each Transport DLL must implement the interfaces derived from the IStrideTransport class.

	Refer to the [[Media:s2sTransport.pdf\|STRIDE Host Runtime Transport Specification]] document for a more detailed description of the Host Transport Services.		Refer to the [[Media:s2sTransport.pdf\|STRIDE Host Runtime Transport Specification]] document for a more detailed description of the Host Transport Services.

	~~=== The Transport Server Object Model ===~~

	The Transport Server is an out-of-process COM server that provides connection management, loopback and diagnostic features. It can be accessed by clients through the STRIDE.transport Program ID. The Transport Server API is defined in the [[Transport Server Component\|Transport Server Object Model]] page.

	== The Transport Server ==		== The Transport Server ==

Ivailop: /* The Host Transport Services */

2009-06-05T00:32:53Z

The Host Transport Services

← Older revision		Revision as of 00:32, 5 June 2009
Line 3:		Line 3:
	== The Host Transport Services ==		== The Host Transport Services ==

	The Host Transport Services define an interface that enables the STRIDE Runtime on your ~~target~~ to send data to and receive data from the target. The STRIDE Transport Server connects the Transport DLL to the STRIDE Runtime running on the host platform, thus providing indirect access to the target from [[STRIDE Studio]], [[AutoScript]], and other STRIDE applications. Several common transports are already supported within the STRIDE Transport Server, including serial and TCP/IP.		The Host Transport Services define an interface that enables the STRIDE Runtime on your host to send data to and receive data from the target. The STRIDE Transport Server connects the Transport DLL to the STRIDE Runtime running on the host platform, thus providing indirect access to the target from [[STRIDE Studio]], [[AutoScript]], and other STRIDE applications. Several common transports are already supported within the STRIDE Transport Server, including serial and TCP/IP.

	[[Image:Transport diagram.gif\|center\|Host Transport Services Diagram]]		[[Image:Transport diagram.gif\|center\|Host Transport Services Diagram]]