Introduction

The ScriptServer system runs on MS IIS as an ISAPI dll. This means that you can take advantage of all the functionality incorporated in MS IIS, such as Secure Sockets Layer (SSL), Integrated Authentication, and much more.   

The Request Model

1. When a website visitor requests a webpage on the ScriptServer, the request is first received by the MS IIS and then passed on to ScriptServer.
2. ScriptServer will make sure that the user has permission to perform the request operation on the page (read, edit, etc).
3. The requested page will be retrieved from the database
4. If the page is using a template, it will also be retrieved.
5. ScriptServer will then execute the script code of the page (or template) using the content of the page.
6. The result is then returned as one result to the MS IIS, which in turn will return it to the user.

Note that it can be either MS IIS or ScriptServer who initially authenticates the user and performs the log in sequence.

Also note that resources on disc also can be protected by the security system of ScriptServer.

 The important thing about this model is the fact that ScriptServer is always present when a request is made for a ScriptServer page. This means that all requests automatically will be validated against the security permissions of the current user. This also means that the script code of a template will be executed every time a page using that template is requested and that the code could interact with the user and respond or behave differently depending on the properties of the user.

 It is also important to notice that ScriptServer is not an offline tool for building websites, but rather a dynamic, interacting platform.

The tiers of ScriptServer

A ScriptServer solution consists of several tiers. This ensures that each tier can be developed and upgraded separately without interfering with the others.

As stated earlier, ScriptServer runs on MS IIS and MS SQL Server (or MSDE) running on MS Windows 2000 Server in a NT-domain or Active Directory. Upon this, we have the kernel. The kernel consists of several COM-objects, which interact with underlying structure. These COM objects provide an object model to the System Scripts. These scripts make up the interface of ScriptServer and are commonly known as the System Editor, Template Workshop, Field Editor and so on.

The next 2 tiers are where the actual website resides in the shape of templates and modules for the functionality and pages for holding the content. In the case of ScriptServer SBE, the whole intranet portal is made up of templates and modules, which can be customized and expanded without even touching the system tier. The same goes for the content tier, which in turn can be expanded by the intranet users without any knowledge in how to program templates or write scripts.

 Needless to say, with ScriptServer each tier can be worked upon without disturbing the others, so while you continue expanding your client solutions, you can rest assured that the modifications you make will be retained even after a system update.