S/Web Object Model

S/Web User Manual

Links on this page:

S/Web Objects
S/Web Object Model

S/WEB Objects

S/Web was conceived as an object based programming environment and we have attempted to stick to these principles.

Let's explain in "English" the objects involved...

At the beginning the S/Web server is launched

This becomes the SERVER object

The SERVER object exists for the life of the S/Web server.
A user comes along wishing to use the S/Web based site. They successfully (or unsuccessfully) login.
They become the CLIENT object
The CLIENT asks for information from the S/Web server.
This request becomes the SESSION object
The SESSION object can be seen as two parts, an incoming and an outgoing.
The incoming part of the SESSION object spawns
The REQUEST object
The outgoing part of the session object spawns
The RESPONSE object
The RESPONSE object spawns
The DOCUMENT object

The other internal objects have to do with simply interfacing to the REPOSITORY and LH.

S/WEB Object Model

S/Web operates by allowing the developer to manipulate a series of objects. These objects affect all areas of the system. All modifications and interactions must occur through these objects.

Each object is accessed through it's appropriate method. All methods are called from the WWW_EXEC_METHOD program.

Valid System Objects	Description
CACHE	This object handles information relating to the S/WEB cache.
CLIENT	This object handles information relating to the client making the current request.
DOCUMENT	This object handles information relating to a repository based document
LH	This object handles information relating to Linear Hash files
REPOSITORY	This object handles information relating to the S/WEB repository
REQUEST	This object handles information relating to the HTTP request.
RESPONSE	This object handles information relating to the HTTP response.
SERVER	This object handles information relating to this specific running S/WEB server
SESSION	This object handles information relating to the current S/WEB session

[top]