Understanding Web processing - Revision history

JAL: minor formatting

2018-08-07T17:15:49Z

minor formatting

JAL: typo

2016-04-07T21:34:04Z

typo

← Older revision		Revision as of 21:34, 7 April 2016
Line 118:		Line 118:
	</table>		</table>

	When a client enters a URL requesting a particular web resource from <var class="product">Janus Web Server</var>, the way the server is configured will determine whether the request should cause the display of a static web page or the execution of a <var class="product">User Language</var> procedure. One or more “web rules” can be defined in the web server to control how to interpret specific URLs or URL patterns. These rules are described in [[Defining Web rules~~\|“Defining Web rules”~~]].		When a client enters a URL requesting a particular web resource from <var class="product">Janus Web Server</var>, the way the server is configured will determine whether the request should cause the display of a static web page or the execution of a <var class="product">User Language</var> procedure. One or more “web rules” can be defined in the web server to control how to interpret specific URLs or URL patterns. These rules are described in [[Defining Web rules]].

	For instance, a request for <code>/documents/report17.html</code> might very well prompt the server to respond by sending to the client the contents of a procedure named “/documents/report17.html” (or “/DOCUMENTS/REPORT17.HTML” if the <var>[[UPCASE (JANUS DEFINE parameter)\|UPCASE]]</var> parameter, the default, was specified on the <var>JANUS DEFINE</var> command for the port).		For instance, a request for <code>/documents/report17.html</code> might very well prompt the server to respond by sending to the client the contents of a procedure named “/documents/report17.html” (or “/DOCUMENTS/REPORT17.HTML” if the <var>[[UPCASE (JANUS DEFINE parameter)\|UPCASE]]</var> parameter, the default, was specified on the <var>JANUS DEFINE</var> command for the port).

ELowell: /* Serving web pages from within Model 204 */

2016-01-05T22:04:31Z

Serving web pages from within Model 204

← Older revision		Revision as of 22:04, 5 January 2016
Line 94:		Line 94:

	Easier and more economical than a series of <var>Print</var> statements, you		Easier and more economical than a series of <var>Print</var> statements, you
	can also enclose blocks of HTML data within an <var>Html</var> (or <var>Text</var>) statement (see: [[Text_and_Html_statements\|"~~Text_and_Html_statements~~"]]) and an		can also enclose blocks of HTML data within an <var>Html</var> (or <var>Text</var>) statement (see [[Text_and_Html_statements\|"Text and Html statements"]]) and an
	<var>End Html</var> (or <var>End Text</var>) statement. <var>Html</var> (or <var>Text</var>) statement blocks may		<var>End Html</var> (or <var>End Text</var>) statement. <var>Html</var> (or <var>Text</var>) statement blocks may
	contain any <var class="product">Model 204</var> expression, including %variables and $functions.		contain any <var class="product">Model 204</var> expression, including %variables and $functions.

ELowell at 22:00, 5 January 2016

2016-01-05T22:00:10Z

← Older revision		Revision as of 22:00, 5 January 2016
Line 39:		Line 39:
	client-server architecture. Using a browser as the front-end, a client-server system can		client-server architecture. Using a browser as the front-end, a client-server system can
	be built in which each user uses the browser they prefer (most of which are free), and		be built in which each user uses the browser they prefer (most of which are free), and
	application development is concentrated on the server system. No client ~~softwaredistribution~~ is required, and access to the server can be tightly controlled.		application development is concentrated on the server system. No client software distribution is required, and access to the server can be tightly controlled.

	While the client must conform to the limitations of the current HTML standard, the standard is quite flexible, and provides all of the features needed to write sophisticated applications. The HTML standards for current, past, and proposed future implementations can be viewed online through the web at the location that maintains them, http://www.w3.org.		While the client must conform to the limitations of the current HTML standard, the standard is quite flexible, and it provides all of the features needed to write sophisticated applications. The HTML standards for current, past, and proposed future implementations can be viewed online through the web at the location that maintains them, http://www.w3.org.

	==The Janus Web Server solution==		==The Janus Web Server solution==

JAL: /* References and links */

2013-04-23T21:33:43Z

References and links

← Older revision		Revision as of 21:33, 23 April 2013
Line 128:		Line 128:

	<ul>		<ul>
	~~<li>[[:Category:Janus Web Server $functions]]</li>~~
	<li>[[List of Janus Web Server $functions]]</li>		<li>[[List of Janus Web Server $functions]]</li>
	<li>[[Janus Web Server]]</li>		<li>[[Janus Web Server]]</li>

JAL at 00:26, 30 October 2012

2012-10-30T00:26:35Z

JALWiccan: 1 revision

2012-10-30T00:09:06Z

1 revision

← Older revision	Revision as of 00:09, 30 October 2012
(No difference)

JAL: /* Serving web pages from within Model 204 */

2012-10-30T00:08:55Z

Serving web pages from within Model 204

← Older revision		Revision as of 00:08, 30 October 2012
Line 71:		Line 71:
	security and integration.		security and integration.

	For sites that already have applications written in Model 204, the Janus Web Server is		For sites that already have applications written in <var class="product">Model 204</var>, the Janus Web Server is
	the most direct and easily implemented Web solution.		the most direct and easily implemented Web solution.

JAL: /* Serving web pages from within Model 204 */

2012-10-10T21:06:18Z

Serving web pages from within Model 204

JAL2: /* Serving web pages from within Model 204 */

2012-02-23T21:11:25Z

Serving web pages from within Model 204

← Older revision		Revision as of 21:11, 23 February 2012
Line 83:		Line 83:
	In Janus Web Server, this type of web page is simply stored as a procedure in a		In Janus Web Server, this type of web page is simply stored as a procedure in a
	Model 204 file. It can be created and edited using the Model 204 editor, it can be		Model 204 file. It can be created and edited using the Model 204 editor, it can be
	[[Uploading ~~Files~~ to a Janus Web Server\|uploaded to the web server]], or it can be loaded from the mainframe to the web server (as described in [[Loading with the SIRPIPE and SIRPUT ~~Utilities~~\|“Loading with the SIRPIPE and SIRPUT ~~Utilities”~~]].		[[Uploading files to a Janus Web Server\|uploaded to the web server]], or it can be loaded from the mainframe to the web server (as described in [[Loading with the SIRPIPE and SIRPUT utilities\|“Loading with the SIRPIPE and SIRPUT utilities”]].
	Serving static pages is simple and can serve many purposes for presenting		Serving static pages is simple and can serve many purposes for presenting
	information that does not change often.</li>		information that does not change often.</li>
Line 99:		Line 99:

	Even more powerful capabilities can be created by using the Janus Web Server		Even more powerful capabilities can be created by using the Janus Web Server
	functions described in [[Janus Web Server ~~API (~~$functions)\|“Janus Web Server ~~API (~~$~~functions)”~~]]. These		functions described in [[Janus Web Server $functions\|“Janus Web Server $functions”]]. These
	enable the processing of, among other things:		enable the processing of the following, among other things:

	<table class="syntaxTable">		<table class="syntaxTable">
Line 118:		Line 118:
	</table>		</table>

	When a client enters a URL requesting a particular web resource from <var class="product">Janus Web Server</var>, the way the server is configured will determine whether the request should cause the display of a static web page or the execution of a <var class="product">User Language</var> procedure. One or more “web rules” can be defined in the web server to control how to interpret specific URLs or URL patterns. These rules are described in [[“Defining Web ~~Rules”~~]].		When a client enters a URL requesting a particular web resource from <var class="product">Janus Web Server</var>, the way the server is configured will determine whether the request should cause the display of a static web page or the execution of a <var class="product">User Language</var> procedure. One or more “web rules” can be defined in the web server to control how to interpret specific URLs or URL patterns. These rules are described in [[Defining Web rules\|“Defining Web rules”]].

	For instance, a request for <code>/documents/report17.html</code> might very well prompt the server to respond by sending to the client the contents of a procedure named “/documents/report17.html” (or “/DOCUMENTS/REPORT17.HTML” if the <var>UPCASE</var> parameter, the default, was specified on the JANUS DEFINE ~~subcommand~~).		For instance, a request for <code>/documents/report17.html</code> might very well prompt the server to respond by sending to the client the contents of a procedure named “/documents/report17.html” (or “/DOCUMENTS/REPORT17.HTML” if the <var>[[UPCASE (JANUS DEFINE parameter)\|UPCASE]]</var> parameter, the default, was specified on the <var>JANUS DEFINE</var> command for the port).

	Alternatively, a rule can be defined so that a URL causes the execution of a <var class="product">Model 204</var> subsystem or procedure. An example of this type of application is presented in [[“Sample application — command processor”]].		Alternatively, a rule can be defined so that a URL causes the execution of a <var class="product">Model 204</var> subsystem or procedure. An example of this type of application is presented in [[“Sample application — command processor”]].

← Older revision		Revision as of 00:26, 30 October 2012
Line 57:		Line 57:

	Sirius Software wrote the Janus Web Server to solve these problems. The Janus Web		Sirius Software wrote the Janus Web Server to solve these problems. The Janus Web
	Server is a full-featured Hypertext Transfer Protocol server running inside a Model 204		Server is a full-featured Hypertext Transfer Protocol server running inside a <var class="product">Model 204</var>
	region under either the MVS or VM operating system. The Janus Web Server uses		region under either the MVS or VM operating system. The Janus Web Server uses
	command-level Janus subcommands to define rules on how the server will operate, and		command-level Janus subcommands to define rules on how the server will operate, and
	an application-level API to process forms and handle complex database server issues.		an application-level API to process forms and handle complex database server issues.
	Instead of PERL or C coding, forms can be written and replied to using Model 204's		Instead of PERL or C coding, forms can be written and replied to using <var class="product">Model 204</var>'s
	native language, User Language.		native language, User Language.

	The Janus Web Server has all the features of other web servers but is tightly integrated		The Janus Web Server has all the features of other web servers but is tightly integrated
	with the high-performance Model 204 database and makes full use of the security and		with the high-performance <var class="product">Model 204</var> database and makes full use of the security and
	speed of the Janus TCP/IP Base. While the Janus Web Server can be used to serve up		speed of the Janus TCP/IP Base. While the Janus Web Server can be used to serve up
	any content types, from plain text to complex graphics, it's the application level API that		any content types, from plain text to complex graphics, it's the application level API that
Line 82:		Line 82:
	<li>As a “static” page of text containing text and HTML commands.		<li>As a “static” page of text containing text and HTML commands.
	In Janus Web Server, this type of web page is simply stored as a procedure in a		In Janus Web Server, this type of web page is simply stored as a procedure in a
	Model 204 file. It can be created and edited using the Model 204 editor, it can be		<var class="product">Model 204</var> file. It can be created and edited using the <var class="product">Model 204</var> editor, it can be
	[[Uploading files to a Janus Web Server\|uploaded to the web server]], or it can be loaded from the mainframe to the web server (as described in [[Loading with the SIRPIPE and SIRPUT utilities\|“Loading with the SIRPIPE and SIRPUT utilities”]].		[[Uploading files to a Janus Web Server\|uploaded to the web server]], or it can be loaded from the mainframe to the web server (as described in [[Loading with the SIRPIPE and SIRPUT utilities\|“Loading with the SIRPIPE and SIRPUT utilities”]].
	Serving static pages is simple and can serve many purposes for presenting		Serving static pages is simple and can serve many purposes for presenting

← Older revision		Revision as of 21:06, 10 October 2012
Line 87:		Line 87:
	information that does not change often.</li>		information that does not change often.</li>

	<li>As a page that is “dynamically” built within User Language, a more powerful yet still		<li>As a page that is “dynamically” built within <var class="product">User Language</var>, a more powerful yet still
	quite simple approach.		quite simple approach.
	One way to do this is to route the output of User Language ~~PRINT~~ statements to the		One way to do this is to route the output of <var class="product">User Language</var> <var>Print</var> statements to the
	client's browser. By “printing” HTML commands among the other data being		client's browser. By “printing” HTML commands among the other data being
	“printed,” a <var class="product">User Language</var> procedure can be quickly converted into an attractive web page.		“printed,” a <var class="product">User Language</var> procedure can be quickly converted into an attractive web page.

	Easier and more economical than a series of <var>Print</var> statements, you		Easier and more economical than a series of <var>Print</var> statements, you
	can also enclose blocks of HTML data within an <var>~~HTML~~</var> (or <var>~~TEXT~~</var>) statement (see: [[Text_and_Html_statements]]) and an		can also enclose blocks of HTML data within an <var>Html</var> (or <var>Text</var>) statement (see: [[Text_and_Html_statements\|"Text_and_Html_statements"]]) and an
	<var>End Html</var> (or <var>End Text</var>) statement. <var>~~HTML~~</var> (or <var>~~TEXT~~</var>) statement blocks may		<var>End Html</var> (or <var>End Text</var>) statement. <var>Html</var> (or <var>Text</var>) statement blocks may
	contain any <var class="product">Model 204</var> expression, including %variables and $functions.		contain any <var class="product">Model 204</var> expression, including %variables and $functions.

	Even more powerful capabilities can be created by using the Janus Web Server		Even more powerful capabilities can be created by using the <var class="product">Janus Web Server</var>
	functions described in [[Janus Web Server $functions\|“Janus Web Server $functions”]]. These		functions described in [[Janus Web Server $functions\|“Janus Web Server $functions”]]. These
	enable the processing of the following, among other things:		enable the processing of the following, among other things:

	<table ~~class="syntaxTable"~~>		<table>
	<tr>		<tr>
	<th>HTML forms</th>		<th>HTML forms</th>
	<td>These provide a mechanism for creating powerful graphical interfaces for data entry and data presentation, which can significantly extend the options available over standard 3270 interfaces.</td></tr>		<td>These provide a mechanism for creating powerful graphical interfaces for data entry and data presentation, which can significantly extend the options available over standard 3270 interfaces.</td></tr>
	<tr>		<tr>
	<th>URL parameters</th>		<th nowrap>URL parameters</th>
	<td>Also known as “isindex data,” this provides an alternative mechanism from form fields to encapsulate data entered on a form or data generated by a web application but to be passed		<td>Also known as “isindex data,” this provides an alternative mechanism from form fields to encapsulate data entered on a form or data generated by a web application but to be passed
	around to different URLs.</td></tr>		around to different URLs.</td></tr>
Line 122:		Line 122:
	For instance, a request for <code>/documents/report17.html</code> might very well prompt the server to respond by sending to the client the contents of a procedure named “/documents/report17.html” (or “/DOCUMENTS/REPORT17.HTML” if the <var>[[UPCASE (JANUS DEFINE parameter)\|UPCASE]]</var> parameter, the default, was specified on the <var>JANUS DEFINE</var> command for the port).		For instance, a request for <code>/documents/report17.html</code> might very well prompt the server to respond by sending to the client the contents of a procedure named “/documents/report17.html” (or “/DOCUMENTS/REPORT17.HTML” if the <var>[[UPCASE (JANUS DEFINE parameter)\|UPCASE]]</var> parameter, the default, was specified on the <var>JANUS DEFINE</var> command for the port).

	Alternatively, a rule can be defined so that a URL causes the execution of a <var class="product">Model 204</var> subsystem or procedure. An example of this type of application is presented in [[~~“Sample~~ application — command ~~processor”~~]].		Alternatively, a rule can be defined so that a URL causes the execution of a <var class="product">Model 204</var> subsystem or procedure. An example of this type of application is presented in [[Janus Web Server application example#Sample application: command processor\|"Sample application: command processor"]].
	</ul>		</ul>