What is WebNet?

An overview of what WebNet is trying to achieve.

WebNet is best looked on as an Internet Forms Server providing a backend database facility.

Looking at it another way, what is it not? It is not an application server, we use Zope for that, it is not a database server, we use MySQL for that and not an HTML server, we use Apache for that.

WebNet will produce dynamic web pages for delivery to Apache for delivery to the browser. The user uses the browser to design catagorised data pages that will best break down the information that is being stored and retrieved. Once the tree structured categories have been established the user can then create multiple web pages that contain data properties, in the shape of HTML forms, from each category for posting data through the web to be stored in the backend SQL database. This data is then available for retrieval through the browser by the public using non password protected back door entry or privately through the front door password protected entry method.

WebNet is written in the Rexx scripting language and uses the fValidate javascript forms validation tool. To facilitate a menu driven entry point WebNet uses the Milonic DHTML javascript product. Everything about WebNet is dynamic, there are no static web pages. HTML pages are built on the fly depending on the page Id (PID) that has been chosen to be rendered. Any page that you see using WebNet has a Rexx script sitting behind it orchestrating the action depending on user interaction. These Rexx scripts are themselves written on the fly as a result of Page Maintenance. These Rexx scripts will also write the javascript parameters to be fed into the javascript products mentioned above. The Category Maintenance will build the Milonic parameters and Data Maintenace will provide the fValidate parameters.