| | | | |
| |
|  |  | |
|
S/Web requires a web server capable of running ISAPI or Perl Scripts. The web server must be able to read/write/delete rights to a drive\path location accessible by the Linear Hash application. Each Advanced Revelation server requires 4 megabytes of EMS memory. Each additional Advanced Revelation server requires an additional 4 megabytes of EMS memory available on the workstation. We do not recommend running more than five instances of Advanced Revelation on a single CPU. Each OpenInsight server requires approximately 6 megabytes of memory. Multiple OpenInsight servers can be run on a single CPU on the Microsoft Windows NT platforms (NT 4.x and Windows 2000). To enable this functionality, you must allow OpenInsight to run in a separate memory space.
S/Web.DLL is a remarkably simple product. S/Web.DLL communicates with the web server using basic CGI/ISAPI commands. The request header and request content are written by the SWEB.DLL/Perl Script to the shared REQUEST directory. The LH Server portion checks this directory for new requests and calls the defined R/BASIC or Basic+ subroutine. This subroutine performs the processing required and returns a valid HTTP response. The LH Server then writes the response header and response content to the shared RESPONSE directory. The SWEB.DLL/Perl Script then returns the response back to the client. The power of the S/Web comes in the functionality and programs included in the product, along with the ability to customize the various parameters and functionality of the system. These features will be outlined in the rest of the document. The S/Web R/BASIC and Basic+ Processor The bulk of the processing of S/Web occurs in the R/BASIC and Basic+ programming modules. R/BASIC and Basic+ will be used interchangeably throughout the rest of this document. SWeb works by allowing the programmer to create and manipulate the various S/Web objects provided. S/Web contains 9 default objects, Cache, Client, Document, LH, Repository, Request, Response, Server and Session. All S/Web functionality is obtained through the use of these objects. These methods are fully documented in S/Web Objects. There is an accessor program, WWW_EXEC_METHOD that controls all access to the S/Web objects. Whilst it is possible to call the individual functions directly, we strongly recommend accessing all object through the WWW_EXEC_METHOD. Sprezzatura will not change the access methods from this function. However, we may change direct object calls at any time in the future. As the saying goes, he who lives by the undocumented feature, dies by the undocumented feature. S/Web does more than return HTML documents. It can return any valid HTTP request. These requests can be generated through R/BASIC or you can retrieve stored documents already existing on a disk. Documents existing on disk can be read through the OSREAD or OSBREAD commands or through the S/WEB Repository. You can find more information about the S/Web repository in S/Web Features. Many documents that you serve back to the browser will need to be customized or personalized for the specific user. There are various techniques the developer can use to create this personalisation. Remember, R/BASIC is a powerful string handling language and your HTML document is primarily made up of strings. Do not be afraid to use the power of R/BASIC to manipulate the document. At Sprezzatura, the most popular way to personalize an HTML document is through swapping tokens. <html> The <$$=LOGINID$$> is an S/Web preprocessor document. For information on this feature can be found in Chapter 4. For now, just assume that this will insert the logged in user's name. %%AMTLEFT%% is a swappable token. We use this value as a placeholder setting and swap it out with the real value in our code. ..... S/Web interacts with your Linear Hash data files as any other R/BASIC program, since it is, after all, an R/BASIC program. You can use standard R/BASIC commands or the LH object.
| | | |
| Copyright © 2005 The Sprezzatura Group. All rights reserved. | |
