WebPublisher - How it works
WebPublisher handles WWW requests in one of three ways (depending on how published libraries are configured). If WebPublisher is capable of responding to the request (ie. it is published from one of the shared libraries) then one of the following events will occur:

1. A Macro matching the URI is run

2. A stored HTML page or image is returned to the browser

3. The request is redirected to another user-defined address

If WebPublisher is unable to satisfy the request then it will either...

1. Redirect the request to a designated HTTP Server, if assigned

2. Return a Page Not Found (404) message to the browser if no other server is designated.

The published content of WebPublisher will depend on how any shared Database libraries are configured. Shared libraries contain the usual mix of Omnis content each library allows HTML and Images (GIF/Jpeg etc.) to be stored as records in addition to any other custom tables, data, and executable code. Omnis programmers can use WebPublisher templates to create database libraries that can be published using WebPublisher.

>>Hard Coded Macro
demonstrates a Code Resource returning a value hard wired into the Omnis procedure.

>>Poke Today's Date
demonstrates a Code Resource poking a value into a variable on a pre-formatted template.

>>Poke a String
demonstrates a Code Resource returning text passed as a variable using a Code Snippet.

>>Do CGI Post Form
demonstrates acquisition of data using Forms and a CGI Post Method.

>>Do CGI Get
demonstrates searching for data using embedded hyperlinks and a CGI Get Method.