GNTicker Trace Protocol - Revision history

Vassia Atanassova: /* General principles */

2009-04-26T20:11:10Z

General principles

← Older revision		Revision as of 23:11, 26 April 2009
Line 11:		Line 11:

	== General principles ==		== General principles ==
	GNTP uses the design of the [[wikipedia:Hypertext Transfer Protocol (HTTP)\|Hypertext Transfer Protocol]] for the presentation layer and [[wikipedia:XML\|XML]] for the application layer. GNTP messages are requests (issued by the client) and responses (issued by the server). Each message consists of the message preamble (protocol version and method name or response code), optional message headers and message body. The message body, if non-empty, is usually an XML document. The namespace used by the XML documents is the [[wikipedia:XML namespace\|GN definitions namespace]]: ''<nowiki>http://www.clbme.bas.bg/GN</nowiki>'', which is defined in the following [[~~GN schema~~\|XML schema]].		GNTP uses the design of the [[wikipedia:Hypertext Transfer Protocol (HTTP)\|Hypertext Transfer Protocol]] for the presentation layer and [[wikipedia:XML\|XML]] for the application layer. GNTP messages are requests (issued by the client) and responses (issued by the server). Each message consists of the message preamble (protocol version and method name or response code), optional message headers and message body. The message body, if non-empty, is usually an XML document. The namespace used by the XML documents is the [[wikipedia:XML namespace\|GN definitions namespace]]: ''<nowiki>http://www.clbme.bas.bg/GN</nowiki>'', which is defined in the following [[GNschema.xsd\|XML schema]].

	A request to the TS should be formed according to the following template:		A request to the TS should be formed according to the following template:

Vassia Atanassova at 20:09, 26 April 2009

2009-04-26T20:09:14Z

Show changes

Vassia Atanassova: /* Class 2 - Successfully completed request */

2009-04-26T19:59:01Z

Class 2 - Successfully completed request: <div style="padding: 10px; border:1px dotted #AAAAAA;">

← Older revision		Revision as of 22:59, 26 April 2009
Line 332:		Line 332:
	\|}		\|}

			<div style="padding: 10px; border:1px dotted #AAAAAA;">
	; Example		; Example
	<i>Client:</i>		<i>Client:</i>
Line 364:		Line 365:
	; Comment		; Comment
	: The TS has executed steps from 0 to 9 inclusive. On step 2 the "Product" token has entered place "L1" with the specified characteristics. On step 3 the "Client1" has moved to place "L2" and token "Client2" has left the GN through place "L5".		: The TS has executed steps from 0 to 9 inclusive. On step 2 the "Product" token has entered place "L1" with the specified characteristics. On step 3 the "Client1" has moved to place "L2" and token "Client2" has left the GN through place "L5".
			</div>

	=== Class 3 - More information needed ===		=== Class 3 - More information needed ===

Vassia Atanassova: /* Response codes */ to the end

2009-04-26T19:53:36Z

Response codes: to the end

Show changes

Vassia Atanassova: /* Response codes */

2009-04-26T19:34:44Z

Response codes

@@ Line 287: / Line 287: @@
 == Response codes ==
 === Class 1 - Invalid request ===
 === Class 2 - Successfully completed request ===
 === Class 3 - More information needed ===
 === Class 4 - Message body errors ===

Vassia Atanassova: /* STEP */

2009-04-26T19:23:49Z

STEP

← Older revision		Revision as of 22:23, 26 April 2009
Line 144:		Line 144:

	; Description		; Description
	: Clients should use STEP in order to execute a number of GN steps of a previously loaded GN. If the parameter is omitted, a default value of 1 is presumed by default. If all the steps are executed correctly, the server responds with an XML document, describing all events in the GN during these steps. The STEP method does not require a message body.		: Clients should use <tt>STEP</tt> in order to execute a number of GN steps of a previously loaded GN. If the parameter is omitted, a default value of 1 is presumed by default. If all the steps are executed correctly, the server responds with an XML document, describing all events in the GN during these steps. The <tt>STEP</tt> method does not require a message body.

	; Example		; Example

Vassia Atanassova: /* Methods */

2009-04-26T19:22:35Z

Methods

Show changes

Vassia Atanassova: /* Methods */

2009-04-26T17:58:06Z

Methods

@@ Line 78: / Line 78: @@
 == Methods ==
 === INIT ===
 === HALT ===
 === STEP ===
 === STEPUNTIL ===
@@ Line 84: / Line 137: @@
 === INPUT ===
 === SAVE ===
 == Response codes ==

Vassia Atanassova: /* Headers */

2009-04-26T17:31:53Z

Headers

@@ Line 56: / Line 56: @@
 == Headers ==
 === Content-Length ===
 === Content-Type ===
 == Methods ==

Vassia Atanassova: New page:
TOC
'''GNTicker Trace Protocol''' (GNTP) is designed to allow two-way communication between the GNTicker server (TS) and its clien...

2009-04-26T17:29:18Z

New page: <div style="float:right; margin-left: .5em">__TOC__</div> '''GNTicker Trace Protocol''' (GNTP) is designed to allow two-way communication between the GNTicker server (TS) and its clien...

New page

<div style="float:right; margin-left: .5em">__TOC__</div>
'''GNTicker Trace Protocol''' (GNTP) is designed to allow two-way communication between the [[GNTicker]] server (TS) and its clients. The main tasks which can be accomplished using GNTP are:
* Sending a [[generalized net]] definition to the TS
* Receiving events for token movement, entrance, leaving or merging from the TS
* Performing a number of steps of the GN execution
* Executing the GN until a specific event occurs, with an upper bound of the number of steps
* Providing client-initiated (active) input in the form of a token, which can be placed in a fixed input place of the GN
* Providing server-initiated (passive) input in the form of a string or double value with a query string
* Client or server initiated halting of the execution
* Error reporting from the TS on all requests

== General principles ==
GNTP uses the design of the [[wikipedia:Hypertext Transfer Protocol (HTTP)|Hypertext Transfer Protocol]] for the presentation layer and [[wikipedia:XML|XML]] for the application layer. GNTP messages are requests (issued by the client) and responses (issued by the server). Each message consists of the message preamble (protocol version and method name or response code), optional message headers and message body. The message body, if non-empty, is usually an XML document. The namespace used by the XML documents is the [[wikipedia:XML namespace|GN definitions namespace]]: ''<nowiki>http://www.clbme.bas.bg/GN</nowiki>'', which is defined in the following [[GN schema|XML schema]].

A request to the TS should be formed according to the following template:
<pre>
<GNTP-request> ::= GNTP/<protocol-version>\r\n
<method-name> <method-parameters>\r\n
(<header>\r\n)*
\r\n
<request-body>

<protocol-version> ::= <decimal-digit>.<decimal-digit>

<method-name> ::= <capital-latin-letter> |
<capital-latin-letter><method-name>

<method-parameters> ::= <decimal-number> |
<decimal-number> <method-parameters>

<header> ::= <header-name>: <header-value>
</pre>

The GNTP headers will be presented in [[#Headers|Headers]]. The method syntax will be presented in [[#Methods|Methods]]. A response from the TS should be formed according to the following template:

<pre>
<GNTP-response> ::=
GNTP/<protocol-version>\r\n
<response-code> <response-details>\r\n
(<header>\r\n)*
\r\n
<response-body>

<response-code> ::=
<response-class><response-type>

<response-class> ::= <decimal-digit>

<response-type> ::= <decimal-digit><decimal-digit>

<response-details> ::= <ANSI-string>
</pre>

The response codes and details will be presented in [[#Response codes|Response codes]].

== Headers ==
=== Content-Length ===
=== Content-Type ===

== Methods ==
=== INIT ===
=== HALT ===
=== STEP ===
=== STEPUNTIL ===
=== TOKENS ===
=== INPUT ===
=== SAVE ===

== Response codes ==
=== Class 1 - Invalid request ===
=== Class 2 - Successfully completed request ===
=== Class 3 - More information needed ===
=== Class 4 - Message body errors ===
=== Class 5 - GNTicker interpreter errors ===

== References ==
* [http://debian.fmi.uni-sofia.bg/~spooler/gnticker/gntp.html GNTicker Trace Protocol (GNTP)]

[[Category:Generalized nets]]
[[Category:Software]]

GNTicker Trace Protocol - Revision history

Vassia Atanassova: /* General principles */

Vassia Atanassova at 20:09, 26 April 2009

Vassia Atanassova: /* Class 2 - Successfully completed request */

Vassia Atanassova: /* Response codes */ to the end

Vassia Atanassova: /* Response codes */

Vassia Atanassova: /* STEP */

Vassia Atanassova: /* Methods */

Vassia Atanassova: /* Methods */

Vassia Atanassova: /* Headers */

Vassia Atanassova: New page: __TOC__ '''GNTicker Trace Protocol''' (GNTP) is designed to allow two-way communication between the GNTicker server (TS) and its clien...

Vassia Atanassova: New page:
TOC
'''GNTicker Trace Protocol''' (GNTP) is designed to allow two-way communication between the GNTicker server (TS) and its clien...