Method procedures — A set of standard SpeedScript procedures that provides a variety of services to Web objects. Some method procedures that duplicate API functions are supported for upward compatibility with earlier WebSpeed versions. Others provide unique services to some types of Web objects, such as main-lining the response to Web requests. Some of these you can customize for each Web object. The source for many of the standard method procedures resides in the utility object web-util.p under install-ath/src/web/objects. The run-web-object procedure follows a protocol designed to ensure the integrity of the Web object, whether it is stateless or state-aware. This allows WebSpeed to manage Web objects in a consistent manner. The run-web-object method procedure is defined in the utility object, install-path/src/web/objects/web-util.p.

Control handlers — A special class of procedures that execute in response to pseudo events in HTML-mapping Web objects, and that you can customize. These pseudo event procedures include web.input and web.output. By overriding web.input and web.output, you can replace the default data movement between HTML field definitions and corresponding field objects for HTML-mapping Web objects. The default versions of these control handlers for each type of HTML field are located in the tagmap utilities under install-path/src/web/support. Each utility procedure understands how to convert data between a particular type of HTML form element and a SpeedScript field object of the corresponding type.

tagmap.dat — A file that contains default mappings between HTML form element types and SpeedScript field object types for HTML-mapping Web objects. Each entry in the file includes the location of the default web.input and web.output control handler procedure for the field mapping. This file is also where you can define your own mappings and custom tags for your application. This file resides in your WebSpeed installation directory (install-path/).

web-disp.p — The control program that runs on all WebSpeed agents and executes all Web objects. The SpeedScript source resides in install-path/src/web/object. It manages various transaction states that can affect the whole application. This SpeedScript procedure is included with the development environment because it is central to the operation of WebSpeed applications. How web-disp.p manages Web objects can affect how and when you might set and evaluate transaction states in each Web object. This program also initializes the utility object web-util.p (residing in the same directory), where most API functions and method procedures reside at run time. WebSpeed has a special set of procedure-calling conventions. The first convention relies on the run-web-object method procedure. This procedure is the standard method to execute a Web object from within another procedure. It is also the basic method web-disp.p uses to execute Web objects in response to Web requests.