Studio:SCL Overview - Revision history

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

2009-08-21T00:09:59Z

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

← Older revision		Revision as of 00:09, 21 August 2009
Line 76:		Line 76:
	*For detailed instructions on working with SCL, including code samples and examples, refer to the [[Media:s2sSCLReferenceGuide.pdf\|SCL Reference Guide]].		*For detailed instructions on working with SCL, including code samples and examples, refer to the [[Media:s2sSCLReferenceGuide.pdf\|SCL Reference Guide]].

	[[Category: SCL]]		[[Category:Studio:SCL]]

Timd: SCL Overview moved to Studio:SCL Overview

2009-08-18T22:48:51Z

SCL Overview moved to Studio:SCL Overview

← Older revision	Revision as of 22:48, 18 August 2009
(No difference)

Ivailop: /* Owners and Users */

2009-02-12T18:16:54Z

Owners and Users

← Older revision		Revision as of 18:16, 12 February 2009
Line 18:		Line 18:
	* An '''owner''' is the called function or message destination. It identifies where function calls or messages are routed, whether it be to the original on-target function or receiver, to a window in [[STRIDE Studio]], or to a script running in Studio. Only one owner is allowed at any given time, with one exception: broadcast messages can originate with one or more owners (subscribers) and terminate (be subscribed to) by one or more users.		* An '''owner''' is the called function or message destination. It identifies where function calls or messages are routed, whether it be to the original on-target function or receiver, to a window in [[STRIDE Studio]], or to a script running in Studio. Only one owner is allowed at any given time, with one exception: broadcast messages can originate with one or more owners (subscribers) and terminate (be subscribed to) by one or more users.

	* A '''user''' makes calls to a function or sends messages to an owner, which can be the original on-target function or receiver, a window in STRIDE Studio, or a script running in Studio. There can be as many users as necessary.		* A '''user''' makes calls to a function or sends messages to an owner, which can be the original on-target function or receiver, a window in [[STRIDE Studio]], or a script running in Studio. There can be as many users as necessary.

	[[Image:Interfaces.gif\|center]]		[[Image:Interfaces.gif\|center]]

Ivailop: /* Owners and Users */

2009-02-12T18:13:04Z

Owners and Users

← Older revision		Revision as of 18:13, 12 February 2009
Line 16:		Line 16:
	The SCM assumes that there is an owner/user relationship between the components communicating across an interface. An '''owner''' provides services to others, while a '''user''' consumes services provided by the owner.		The SCM assumes that there is an owner/user relationship between the components communicating across an interface. An '''owner''' provides services to others, while a '''user''' consumes services provided by the owner.

	* An '''owner''' is the called function or message destination. It identifies where function calls or messages are routed, whether it be to the original on-target function or receiver, to a window in STRIDE Studio, or to a script running in Studio. Only one owner is allowed at any given time, with one exception: broadcast messages can originate with one or more owners (subscribers) and terminate (be subscribed to) by one or more users.		* An '''owner''' is the called function or message destination. It identifies where function calls or messages are routed, whether it be to the original on-target function or receiver, to a window in [[STRIDE Studio]], or to a script running in Studio. Only one owner is allowed at any given time, with one exception: broadcast messages can originate with one or more owners (subscribers) and terminate (be subscribed to) by one or more users.

	* A '''user''' makes calls to a function or sends messages to an owner, which can be the original on-target function or receiver, a window in STRIDE Studio, or a script running in Studio. There can be as many users as necessary.		* A '''user''' makes calls to a function or sends messages to an owner, which can be the original on-target function or receiver, a window in STRIDE Studio, or a script running in Studio. There can be as many users as necessary.

Stevel: /* See Also */

2008-10-08T20:26:29Z

See Also

← Older revision		Revision as of 20:26, 8 October 2008
Line 74:		Line 74:
	*[[SCL Message Attributes]]		*[[SCL Message Attributes]]
	*[[SCL Pragmas]]		*[[SCL Pragmas]]
	*For detailed instructions on working with SCL, including code samples and examples, refer to the [~~http~~:~~//www.s2technologies.com/pdf/~~s2sSCLReferenceGuide.pdf SCL Reference Guide].		*For detailed instructions on working with SCL, including code samples and examples, refer to the [[Media:s2sSCLReferenceGuide.pdf\|SCL Reference Guide]].

	[[Category: SCL]]		[[Category: SCL]]

Ivailop: /* See Also */

2008-10-02T18:08:58Z

See Also

← Older revision		Revision as of 18:08, 2 October 2008
Line 76:		Line 76:
	*For detailed instructions on working with SCL, including code samples and examples, refer to the [http://www.s2technologies.com/pdf/s2sSCLReferenceGuide.pdf SCL Reference Guide].		*For detailed instructions on working with SCL, including code samples and examples, refer to the [http://www.s2technologies.com/pdf/s2sSCLReferenceGuide.pdf SCL Reference Guide].

	[[Category: ~~Reference~~]]		[[Category: SCL]]

Ivailop: /* See Also */

2008-10-02T15:34:24Z

See Also

← Older revision		Revision as of 15:34, 2 October 2008
Line 74:		Line 74:
	*[[SCL Message Attributes]]		*[[SCL Message Attributes]]
	*[[SCL Pragmas]]		*[[SCL Pragmas]]
	*For detailed instructions on working with SCL, including code samples and examples, refer to the [[http://www.s2technologies.com/pdf/s2sSCLReferenceGuide.pdf SCL Reference Guide]].		*For detailed instructions on working with SCL, including code samples and examples, refer to the [http://www.s2technologies.com/pdf/s2sSCLReferenceGuide.pdf SCL Reference Guide].

	[[Category: Reference]]		[[Category: Reference]]

Stevel: /* See Also */

2008-07-25T19:21:42Z

See Also

← Older revision		Revision as of 19:21, 25 July 2008
Line 69:		Line 69:

	== See Also ==		== See Also ==
	:For detailed instructions on working with SCL, including code samples and examples, refer to the SCL Reference Guide.		*[[SCL Structure]]
	~~:SCL Structure~~		*[[SCL Data Types]]
	~~:SCL Data Types~~		*[[SCL Design Requirements]]
	~~:SCL Design Requirements~~		*[[SCL Message Attributes]]
	~~:SCL Message Attributes~~		*[[SCL Pragmas]]
	~~:SCL Pragmas~~		*For detailed instructions on working with SCL, including code samples and examples, refer to the [[http://www.s2technologies.com/pdf/s2sSCLReferenceGuide.pdf SCL Reference Guide]].

	[[Category: Reference]]		[[Category: Reference]]

Stevel: /* The STRIDE Communication Language (SCL) */

2008-07-25T19:20:11Z

The STRIDE Communication Language (SCL)

← Older revision		Revision as of 19:20, 25 July 2008
Line 56:		Line 56:
	The STRIDE Communication Language (SCL) is an Interface Definition Language, or IDL, used by the SCM to identify and define messages, remote function calls (RFCs), and trace points within an application. Interfaces are identified and annotated in order to expose enough information about them so that they can be marshaled across platform boundaries. SCL-compliant messages also define a contract between the communicating owner and user. The syntax and semantics of this contract are described below.		The STRIDE Communication Language (SCL) is an Interface Definition Language, or IDL, used by the SCM to identify and define messages, remote function calls (RFCs), and trace points within an application. Interfaces are identified and annotated in order to expose enough information about them so that they can be marshaled across platform boundaries. SCL-compliant messages also define a contract between the communicating owner and user. The syntax and semantics of this contract are described below.

	The SCL is a superset of the ANSI C language. SCL extensions to the C language are a set of pragmas that allow interface semantics to be more precisely prescribed than allowed by the C language.		The SCL is a superset of the ANSI C language. SCL extensions to the C language are a set of [[SCL_Pragmas\|pragmas]] that allow interface semantics to be more precisely prescribed than allowed by the C language.

	* Message-based interfaces require unique identification of the message, definition of the sender/receiver relationship, and description of the data, if any, that is part of the message payload.		* Message-based interfaces require unique identification of the message, definition of the sender/receiver relationship, and description of the data, if any, that is part of the message payload.
Line 62:		Line 62:
	* Trace points require unique identification of the trace point, assignment of a name, and description of the optional associated data.		* Trace points require unique identification of the trace point, assignment of a name, and description of the optional associated data.

	SCL is a superset of the ANSI C Standard (ISO/IEC 9899:1999). Primarily, the extensions consist of new pragma directives. For detailed information about SCL Pragmas, click here. The context for this description is the ANSI C Standard (ISO/IEC 9899:1999). Many terms used within this section have meaning as defined by the standard.		SCL is a superset of the ANSI C Standard (ISO/IEC 9899:1999). Primarily, the extensions consist of new pragma directives. For detailed information about SCL Pragmas, click [[SCL_Pragmas\|here]]. The context for this description is the ANSI C Standard (ISO/IEC 9899:1999). Many terms used within this section have meaning as defined by the standard.

	An SCL-compliant compiler automatically defines the symbol "_SCL".		An SCL-compliant compiler automatically defines the symbol "_SCL".

	'''Note:''' C++-style tag names for enumerations, structures, and unions are supported.		'''Note:''' C++-style tag names for enumerations, structures, and unions are supported.

	== See Also ==		== See Also ==

Stevel: /* Owners and Users */

2008-07-25T19:17:39Z

Owners and Users

← Older revision		Revision as of 19:17, 25 July 2008
Line 14:		Line 14:

	==== Owners and Users ====		==== Owners and Users ====
	The SCM assumes that there is an owner/user relationship between the components communicating across an interface. An '''owner''' provides services to others, while a '''user''' consumes services provided by the owner ~~(click here for~~ more ~~information about~~ owners and users).		The SCM assumes that there is an owner/user relationship between the components communicating across an interface. An '''owner''' provides services to others, while a '''user''' consumes services provided by the owner.

			* An '''owner''' is the called function or message destination. It identifies where function calls or messages are routed, whether it be to the original on-target function or receiver, to a window in STRIDE Studio, or to a script running in Studio. Only one owner is allowed at any given time, with one exception: broadcast messages can originate with one or more owners (subscribers) and terminate (be subscribed to) by one or more users.

			* A '''user''' makes calls to a function or sends messages to an owner, which can be the original on-target function or receiver, a window in STRIDE Studio, or a script running in Studio. There can be as many users as necessary.

			[[Image:Interfaces.gif\|center]]

	==== Asynchronous Messaging ====		==== Asynchronous Messaging ====