$Web Proc Send or $Web ProcSend - Revision history

JAL at 22:06, 5 June 2013

2013-06-05T22:06:38Z

← Older revision		Revision as of 22:06, 5 June 2013
Line 9:		Line 9:

	==Syntax==		==Syntax==
	<p class="syntax"><span class="term">%rc</span> = $Web_Proc[_]Send( filename, procname, p_flag )		<p class="syntax"><span class="term">%rc</span> = $Web_Proc[_]Send( <span class="term">filename, procname, p_flag</span> )
	</p>		</p>

JALWiccan: Automatically generated page update

2013-04-10T18:18:20Z

Automatically generated page update

← Older revision		Revision as of 18:18, 10 April 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:$Web_Proc_Send or $Web_ProcSend}}		{{DISPLAYTITLE:$Web_Proc_Send or $Web_ProcSend}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>Add contents of procedure to response~~<section end="desc" />~~</span>		<span class="pageSubtitle">Add contents of procedure to response</span>

	<var>$Web_Proc_Send</var> adds the contents of a procedure to the client buffer.		<var>$Web_Proc_Send</var> adds the contents of a procedure to the client buffer.
Line 9:		Line 9:

	==Syntax==		==Syntax==
	<p class="syntax"~~><section begin="syntax" /~~><span class="term">%rc</span> = $Web_Proc[_]Send( filename, procname, p_flag )		<p class="syntax"><span class="term">%rc</span> = $Web_Proc[_]Send( filename, procname, p_flag )
	~~<section end="syntax" />~~</p>		</p>

	===SYntax terms===		===SYntax terms===

JAL: /* Examples */

2012-10-26T21:05:54Z

Examples

← Older revision		Revision as of 21:05, 26 October 2012
Line 82:		Line 82:
	This sample shows how customized lines of HTML can be interspersed with static bodies of HTML by alternate calls to <var>$Web_ProcSend</var> and <var>$Web_Put_Text</var>. First the procedure SALUTATION is sent to the client buffer from file PROMOS. The MORE flag allows us to continue sending. Next a customized greeting is placed in the buffer, then the body of the document is taken from procedure DUFF_BEER_PROMOTION, again with the MORE flag, then a custom sign-off line, then the end of the HTML document without the MORE flag. </p>		This sample shows how customized lines of HTML can be interspersed with static bodies of HTML by alternate calls to <var>$Web_ProcSend</var> and <var>$Web_Put_Text</var>. First the procedure SALUTATION is sent to the client buffer from file PROMOS. The MORE flag allows us to continue sending. Next a customized greeting is placed in the buffer, then the body of the document is taken from procedure DUFF_BEER_PROMOTION, again with the MORE flag, then a custom sign-off line, then the end of the HTML document without the MORE flag. </p>
	<p>		<p>
	The <var>$~~WEB_PROC_SEND~~</var> without the MORE sends all the content that has been accumulated to that point, followed by the indicated procedure. After everything has been sent, the connection with the client is terminated. Any functions that start with <tt>$Web</tt> that require a connection with the client would cause a user restart after this point, as would any other attempt to communicate with the client. Because of this, there's relatively little that can usually be done after a <var>$~~WEB_PROC_SEND~~</var> without MORE (or a $Web_Done); so it's not atypical, as in this example, for such a call to be followed almost immediately by a STOP statement.</p>		The <var>$Web_Proc_Send</var> without the MORE sends all the content that has been accumulated to that point, followed by the indicated procedure. After everything has been sent, the connection with the client is terminated. Any functions that start with <code>$Web</code> that require a connection with the client would cause a user restart after this point, as would any other attempt to communicate with the client. Because of this, there's relatively little that can usually be done after a <var>$Web_Proc_Send</var> without MORE (or a <var>$Web_Done</var>); so it's not atypical, as in this example, for such a call to be followed almost immediately by a STOP statement.</p>

	[[Category:Janus Web Server $functions\|$Web_ProcSend]]		[[Category:Janus Web Server $functions\|$Web_ProcSend]]

JAL: /* Status codes */

2012-10-26T21:04:42Z

Status codes

← Older revision		Revision as of 21:04, 26 October 2012
Line 61:		Line 61:
	<tr><th>Code</th>		<tr><th>Code</th>
	<th>Meaning</th></tr>		<th>Meaning</th></tr>
	<tr><th>0</th>		<tr><th>  0</th>
	<td>Procedure successfully sent.</td></tr>		<td>Procedure successfully sent.</td></tr>
	<tr><th>-1</th>		<tr><th>-1</th>

JALWiccan: 1 revision

2012-10-26T20:26:23Z

1 revision

← Older revision	Revision as of 20:26, 26 October 2012
(No difference)

JAL: /* Status codes */

2012-10-26T20:26:21Z

Status codes

← Older revision		Revision as of 20:26, 26 October 2012
Line 82:		Line 82:
	This sample shows how customized lines of HTML can be interspersed with static bodies of HTML by alternate calls to <var>$Web_ProcSend</var> and <var>$Web_Put_Text</var>. First the procedure SALUTATION is sent to the client buffer from file PROMOS. The MORE flag allows us to continue sending. Next a customized greeting is placed in the buffer, then the body of the document is taken from procedure DUFF_BEER_PROMOTION, again with the MORE flag, then a custom sign-off line, then the end of the HTML document without the MORE flag. </p>		This sample shows how customized lines of HTML can be interspersed with static bodies of HTML by alternate calls to <var>$Web_ProcSend</var> and <var>$Web_Put_Text</var>. First the procedure SALUTATION is sent to the client buffer from file PROMOS. The MORE flag allows us to continue sending. Next a customized greeting is placed in the buffer, then the body of the document is taken from procedure DUFF_BEER_PROMOTION, again with the MORE flag, then a custom sign-off line, then the end of the HTML document without the MORE flag. </p>
	<p>		<p>
	The $WEB_PROC_SEND without the MORE sends all the content that has been accumulated to that point, followed by the indicated procedure. After everything has been sent, the connection with the client is terminated. Any functions that start with <tt>$Web</tt> that require a connection with the client would cause a user restart after this point, as would any other attempt to communicate with the client. Because of this, there's relatively little that can usually be done after a $WEB_PROC_SEND without MORE (or a $Web_Done); so it's not atypical, as in this example, for such a call to be followed almost immediately by a STOP statement.</p>		The <var>$WEB_PROC_SEND</var> without the MORE sends all the content that has been accumulated to that point, followed by the indicated procedure. After everything has been sent, the connection with the client is terminated. Any functions that start with <tt>$Web</tt> that require a connection with the client would cause a user restart after this point, as would any other attempt to communicate with the client. Because of this, there's relatively little that can usually be done after a <var>$WEB_PROC_SEND</var> without MORE (or a $Web_Done); so it's not atypical, as in this example, for such a call to be followed almost immediately by a STOP statement.</p>

	[[Category:Janus Web Server $functions\|$Web_ProcSend]]		[[Category:Janus Web Server $functions\|$Web_ProcSend]]

JAL: /* Status codes */

2012-10-26T19:22:36Z

Status codes

← Older revision		Revision as of 19:22, 26 October 2012
Line 58:		Line 58:

	===Status codes===		===Status codes===
	<table ~~class="syntaxTable"~~>		<table>
	<tr><th>Code</th>		<tr><th>Code</th>
	<th>Meaning</th></tr>		<th>Meaning</th></tr>

JAL: /* SYntax terms */

2012-10-26T19:22:11Z

SYntax terms

← Older revision		Revision as of 19:22, 26 October 2012
Line 52:		Line 52:

	<tr><th><var>TEXT</var></th>		<tr><th><var>TEXT</var></th>
	<td>Content is treated as plain text: <var class="product">Janus Web Server</var> will translate from EBCDIC to ASCII, regardless of the mime type. :note. Unless you specify TEXT, or unless the output mime type (see [[$Web_Type]]) starts with the string "text/", <var>$Web_ProcSend</var> assumes BINARY.		<td>Content is treated as plain text: <var class="product">Janus Web Server</var> will translate from EBCDIC to ASCII, regardless of the mime type. :note. Unless you specify TEXT, or unless the output mime type (see <var>[[$Web_Type]]</var>) starts with the string "text/", <var>$Web_ProcSend</var> assumes BINARY.
	</td></tr></table>		</td></tr></table>

JAL: /* SYntax terms */

2012-10-26T19:21:16Z

SYntax terms

← Older revision		Revision as of 19:21, 26 October 2012
Line 34:		Line 34:
	<table>		<table>
	<tr><th><var>BINARY</var></th>		<tr><th><var>BINARY</var></th>
	<td>Procedure must be in either the binary or the base64 encoded format used by <var class="product">[[Janus Web Server]]</var>. For further description of these encodings, see <var class="product">[[Janus Web Server]]</var> will perform no EBCDIC to ASCII translation on the contents.</td></tr>		<td>Procedure must be in either the binary or the base64 encoded format used by <var class="product">Janus Web Server</var>. For further description of these encodings, see <var class="product">Janus Web Server</var> will perform no EBCDIC to ASCII translation on the contents.</td></tr>

	<tr><th><var>CR</var></th>		<tr><th><var>CR</var></th>
Line 52:		Line 52:

	<tr><th><var>TEXT</var></th>		<tr><th><var>TEXT</var></th>
	<td>Content is treated as plain text: <var class="product">[[Janus Web Server]]</var> will translate from EBCDIC to ASCII, regardless of the mime type. :note. Unless you specify TEXT, or unless the output mime type (see [[$Web_Type]]) starts with the string "text/", <var>$Web_ProcSend</var> assumes BINARY.		<td>Content is treated as plain text: <var class="product">Janus Web Server</var> will translate from EBCDIC to ASCII, regardless of the mime type. :note. Unless you specify TEXT, or unless the output mime type (see [[$Web_Type]]) starts with the string "text/", <var>$Web_ProcSend</var> assumes BINARY.
	</td></tr></table>		</td></tr></table>

JALWiccan: 1 revision

2012-10-26T19:16:36Z

1 revision

← Older revision	Revision as of 19:16, 26 October 2012
(No difference)