Janus Web Server application coding considerations - Revision history

JAL: minor cleanup

2016-04-07T21:31:09Z

minor cleanup

JAL: typo

2015-06-12T15:38:11Z

typo

← Older revision		Revision as of 15:38, 12 June 2015
Line 994:		Line 994:

	Last Model 204 error :		Last Model 204 error :
	MSIR.0561: $XML_COUNT (argument 2): relative XPath expression based on ~~XMLDoc~~		MSIR.0561: $XML_COUNT (argument 2): relative XPath expression based on XmlDoc
	</p>		</p>
	In the example above, the first error, indicated by		In the example above, the first error, indicated by

JAL at 20:50, 2 September 2014

2014-09-02T20:50:29Z

Show changes

Heikki: /* Server side includes */

2014-05-28T23:37:24Z

Server side includes

← Older revision		Revision as of 23:37, 28 May 2014
Line 582:		Line 582:
	<img src="header.gif">		<img src="header.gif">
	<xmp>		<xmp>
	<!--#exec cmd="MONITOR DISKBUFF"-->		<!--#exec cmd="MONITOR DISKBUFF"-->
	</xmp>		</xmp>
	<img src="trailer.gif">		<img src="trailer.gif">
Line 660:		Line 660:
	<img src="header.gif">		<img src="header.gif">
	<xmp>		<xmp>
	<!--#include file="GOODMORNING.HTML"-->		<!--#include file="GOODMORNING.HTML"-->
	</xmp>		</xmp>
	<img src="trailer.gif">		<img src="trailer.gif">
Line 744:		Line 744:
	URL would see the content of the SSI tag translated, while other		URL would see the content of the SSI tag translated, while other
	viewers would just see the static content.		viewers would just see the static content.

	==URL parameters or isindex data==		==URL parameters or isindex data==
	"Isindex data" is a somewhat obsolete term that has come into disfavor and		"Isindex data" is a somewhat obsolete term that has come into disfavor and

Dme at 16:14, 26 March 2013

2013-03-26T16:14:13Z

← Older revision		Revision as of 16:14, 26 March 2013
Line 71:		Line 71:
	evaluating an <var>ON</var> rule that indicates <var>CMD</var>, the connection is broken		evaluating an <var>ON</var> rule that indicates <var>CMD</var>, the connection is broken
	when a <var>LOGOFF</var> is executed, when processing returns to the <var class="product">Model 204</var>		when a <var>LOGOFF</var> is executed, when processing returns to the <var class="product">Model 204</var>
	command line, when a <var>[[$Web_Done]]</var> is executed, or when a <var>[[$~~Web_ProcSend~~]]</var> is		command line, when a <var>[[$Web_Done]]</var> is executed, or when a <var>[[$Web_Proc_Send]]</var> is
	executed without the <var>MORE</var> parameter.		executed without the <var>MORE</var> parameter.
	==Determining which output is sent to the client==		==Determining which output is sent to the client==
Line 82:		Line 82:
	statement output, <var class="product">Model 204</var> command output)		statement output, <var class="product">Model 204</var> command output)
	may also be mixed with		may also be mixed with
	data sent from procedures via the <var>$~~Web_ProcSend~~</var> function.		data sent from procedures via the <var>$Web_Proc_Send</var> function.

	When processing a command specified with <var>CMD</var> on the port definition,		When processing a command specified with <var>CMD</var> on the port definition,
Line 98:		Line 98:
	<li><var>[[$Web_Flush]]</var>, which indicates that all current		<li><var>[[$Web_Flush]]</var>, which indicates that all current
	response data (captured terminal output and data sent with		response data (captured terminal output and data sent with
	<var>$~~Web_ProcSend~~</var>) is to be discarded.		<var>$Web_Proc_Send</var>) is to be discarded.
	</ul>		</ul>

Line 117:		Line 117:
	<li>Processing returns to the <var class="product">Model 204</var> command line.		<li>Processing returns to the <var class="product">Model 204</var> command line.
	<li>A <var>$Web_Done</var> is executed.		<li>A <var>$Web_Done</var> is executed.
	<li>A <var>$~~Web_Procsend~~</var> is executed without the <var>MORE</var> parameter.		<li>A <var>$Web_Proc_Send</var> is executed without the <var>MORE</var> parameter.
	</ul>		</ul>
	'''Note:'''		'''Note:'''
Line 251:		Line 251:
	This is		This is
	true even when a static procedure is sent back to the browser with a		true even when a static procedure is sent back to the browser with a
	<var>$~~Web_Procsend~~</var>, since there is no guarantee that the URL will always		<var>$Web_Proc_Send</var>, since there is no guarantee that the URL will always
	return the same procedure to the browser.		return the same procedure to the browser.
	For <var>CMD</var> processing,		For <var>CMD</var> processing,
Line 547:		Line 547:
	tags is turned on by specifying the <var>SSI</var> subparameter on the		tags is turned on by specifying the <var>SSI</var> subparameter on the
	<var>[[JANUS WEB ON]]</var> command or		<var>[[JANUS WEB ON]]</var> command or
	on the <var>[[$~~Web_ProcSend~~]]</var> function.		on the <var>[[$Web_Proc_Send]]</var> function.

	A case where SSI is usefully applied is a site designed and built using a site		A case where SSI is usefully applied is a site designed and built using a site
Line 600:		Line 600:
	If the <var>SSI</var> subparameter is not specified on the <var>SEND</var> rule		If the <var>SSI</var> subparameter is not specified on the <var>SEND</var> rule
	for this page		for this page
	(or on the <var>$~~Web_ProcSend~~</var> function if that was used), the page will		(or on the <var>$Web_Proc_Send</var> function if that was used), the page will
	be sent without executing the SSI command, and the browser will see		be sent without executing the SSI command, and the browser will see
	the SSI tag as a comment and will ignore it.		the SSI tag as a comment and will ignore it.
Line 606:		Line 606:
	So, for SSI to work you have to:		So, for SSI to work you have to:
	<ol>		<ol>
	<li>Specify <code>SSI</code> on the <var>JANUS WEB ON</var> rule or <var>$~~Web_ProcSend~~</var> function.		<li>Specify <code>SSI</code> on the <var>JANUS WEB ON</var> rule or <var>$Web_Proc_Send</var> function.
	<li>Place the tags in the HTML where you want the server to fill in		<li>Place the tags in the HTML where you want the server to fill in
	the content.		the content.
Line 715:		Line 715:
	Scanning for server side includes is indicated by the <var>SSI</var> parameter		Scanning for server side includes is indicated by the <var>SSI</var> parameter
	in the <var>JANUS WEB ON ... SEND</var> rule for a URL, or by the <var>SSI</var> parameter		in the <var>JANUS WEB ON ... SEND</var> rule for a URL, or by the <var>SSI</var> parameter
	on a <var>$~~Web_ProcSend~~</var>.		on a <var>$Web_Proc_Send</var>.
	For example:		For example:
	<p class="code">JANUS WEB WEB400 ON /ALEX/* OPEN FILE ALEXPROC SEND * SSI </p>		<p class="code">JANUS WEB WEB400 ON /ALEX/* OPEN FILE ALEXPROC SEND * SSI </p>
	or:		or:
	<p class="code">%x = $~~Web_ProcSend~~( 'ALEXPROC, 'SMILEY.HTML', 'SSI')		<p class="code">%x = $Web_Proc_Send( 'ALEXPROC, 'SMILEY.HTML', 'SSI')
	</p>		</p>

JAL2 at 22:46, 15 September 2011

2011-09-15T22:46:01Z

← Older revision		Revision as of 22:46, 15 September 2011
Line 1:		Line 1:
			== A review of web processing with Janus Web Server==
	Web Servers are generally stateless: the server responds to a single		Web Servers are generally stateless: the server responds to a single
	request and then breaks the connection.		request and then breaks the connection.
Line 15:		Line 15:
	to a <var class="product">User Language</var> application in response to a form.		to a <var class="product">User Language</var> application in response to a form.

	The ~~web~~ functions ~~in the previous chapter~~ allow an application to query the		The [[Janus Web Server $functions]] allow an application to query the
	contents of form headers and a form itself.		contents of form headers and a form itself.
	Headers contain information automatically		Headers contain information automatically
Line 41:		Line 41:
	only source of debugging information is the <var class="product">Model 204</var> journal.		only source of debugging information is the <var class="product">Model 204</var> journal.
	A		A
	journal scanning tool like <var class="product">SirScan</var> is critical to efficient application		journal scanning tool like <var class="product">[http://sirius-software.com/maint/download/scanr.pdf SirScan]</var> is critical to efficient application development.
	development ~~(see the <var class="product">SirScan</var>R for details on this Sirius~~
	~~product)~~.

	The sequence of events in a Web connection is:		The sequence of events in a <var class="product">Janus Web</var> connection is:
	<ol>		<ol>
	<li>The client connects to the server with a URL.		<li>The client connects to the server with a URL.
Line 58:		Line 56:
	for a logon ID and password, or may be forbidden access.		for a logon ID and password, or may be forbidden access.
	<li>The default mime type is set from the matching <var>[[JANUS WEB TYPE\|TYPE]]</var> rule.		<li>The default mime type is set from the matching <var>[[JANUS WEB TYPE\|TYPE]]</var> rule.
	<li>The <var>OPEN</var> and <var>CMD</var> commands on the <var>JANUS DEFINE</var> for the web port are		<li>The <var>OPEN</var> and <var>CMD</var> commands on the <var>[[JANUS DEFINE]]</var> for the web port are
	executed.		executed.
	It is possible that this processing could send a response and		It is possible that this processing could send a response and
Line 73:		Line 71:
	evaluating an <var>ON</var> rule that indicates <var>CMD</var>, the connection is broken		evaluating an <var>ON</var> rule that indicates <var>CMD</var>, the connection is broken
	when a <var>LOGOFF</var> is executed, when processing returns to the <var class="product">Model 204</var>		when a <var>LOGOFF</var> is executed, when processing returns to the <var class="product">Model 204</var>
	command line, when a <var>$Web_Done</var> is executed, or when a <var>$~~Web_Procsend~~</var> is		command line, when a <var>[[$Web_Done]]</var> is executed, or when a <var>[[$Web_ProcSend]]</var> is
	executed without the <var>MORE</var> parameter.		executed without the <var>MORE</var> parameter.
	==Determining which output is sent to the client==		==Determining which output is sent to the client==
Line 84:		Line 82:
	statement output, <var class="product">Model 204</var> command output)		statement output, <var class="product">Model 204</var> command output)
	may also be mixed with		may also be mixed with
	data sent from procedures via the <var>$~~Web_Procsend~~</var> function.		data sent from procedures via the <var>$Web_ProcSend</var> function.

	When processing a command specified with <var>CMD</var> on the port definition,		When processing a command specified with <var>CMD</var> on the port definition,
Line 93:		Line 91:
	These defaults can be overridden by the following $functions:		These defaults can be overridden by the following $functions:
	<ul>		<ul>
	<li><var>$Web_On</var>, which		<li><var>[[$Web_On]]</var>, which
	indicates that terminal output is to be captured and sent back to the		indicates that terminal output is to be captured and sent back to the
	browser as part the request response.		browser as part the request response.
	<li><var>$Web_Off</var>, which indicates that terminal		<li><var>[[$Web_Off]]</var>, which indicates that terminal
	output is to be captured and sent to the audit trail, not to the browser.		output is to be captured and sent to the audit trail, not to the browser.
	<li><var>$Web_Flush</var>, which indicates that all current		<li><var>[[$Web_Flush]]</var>, which indicates that all current
	response data (captured terminal output and data sent with		response data (captured terminal output and data sent with
	<var>$~~Web_Procsend~~</var>) is to be discarded.		<var>$Web_ProcSend</var>) is to be discarded.
	</ul>		</ul>

	In order to be able to send the response length to the browser and to		In order to be able to send the response length to the browser and to
	make <var>$Web_Flush</var> possible, captured response data is saved in the		make <var>[[$Web_Flush]]</var> possible, captured response data is saved in the
	<var class="product">Model 204</var> address space until the request is done.		<var class="product">Model 204</var> address space until the request is done.
	The response length		The response length

JAL2: Created page with " Web Servers are generally stateless: the server responds to a single request and then breaks the connection. The client has to establish another connection to make another requ..."

2011-09-15T22:03:28Z

Created page with " Web Servers are generally stateless: the server responds to a single request and then breaks the connection. The client has to establish another connection to make another requ..."

Show changes