WebHub Release Notes for v1.650
This file was last updated 14 October 1998, 13:33 PST
Note: components were shipped on 12 October and 13 October, both
stating version = v1.65. Nonetheless, there were slight changes
relating to the PARAMS macro and the %=. syntax.
Improvements by Category
No changes relative to v1.62.
In the WebHub VCL Components
- Exporting v1.650
- Pages will export even if the TWebPage had not yet been instantiated.
(Under prior versions you had to instantiate the page to export it.) Now
it instantiates them automatically if the ExportFilename is filled in.
- If you export interactively from an application server (as opposed to
using a web action to trigger exporting), then, at the end of the export process,
a status message will display the number of successfully exported pages
and information about any errors. The specific errors will be available
under AppID|Edit Errors.
- If IIS 4 (or any other process) has a lock on a target export file, then
WebHub will skip that file. In prior versions WebHub would attempt to export
to it anyway, which resulted in files being deleted later, after IIS 4 released
the lock (apparently). In any case, now WebHub will skip the page and enumerate
the error under AppID|Edit Errors.
- IsDynamic is forced to FALSE in ExportStaticPage.
- TWebOutput.Onclose v1.650
Fixed in webcore.dcu; no longer called for session 0.
- twebserver v1.650
DetectTextAreas: Boolean; read/write
DEFAULT FALSE, USED TO BE TRUE
The default processing for textareas in versions prior to this build would
check all incoming literals for CrLf and if they contained CrLf would move
them to textareas regardless of prefix.
This flag serves to indicate that you want unprefixed textareas to remain
KeepAlive: Boolean; read-only.
Indicates if the client requested Connection: Keep-Alive in its request.
This property works in conjunction with the .. next one described:
- TWebOutput v1.650
KeepAlive: Boolean; read/write .. default true
Indicates if you want your server to honor client requests for Connection:
In prior version one used to manually add a header in code or through the
headers macro in order to take advantage of the performance benefits
offered by this flag.
Not recommended for sites with huge numbers of clients as too many open
connections may block new visitors from connecting when they otherwise
could. Turn this off (or add another server) if connections start to get
- TWebServer.ExcludeNameStem v1.650
Defaults to '_' in the constructor, instead of blank. (Help file had been out of sync
with the code.)
- TWebApp.BuiltIns new property v1.650
One can now individually disable built-in pages.
TwhBuiltin = (biSpeed,biSpeedT,
TwhBuiltins = set of TwhBuiltin;
Please note that one can deny any and all of these pages through the
OnBuiltInPage Event, which allows one to set the PageID to something desirable
if TWebCommandline.PageID is unacceptable.
This new property will let the programmer remove any code that might have
done such checking, and help everyone to stop masking those pages.
To make this easy to program, you can set the new property
BuiltInsEnabled true/false in order to set/clear the set of enabled
builtins. (BuiltInsEnabled returns true if _any built-in page is enabled)
- SendFileIIS v1.650
Added support for the
,delete flag, which had been in the help but non-operational.
- Page Footer for Trial Version v1.650
The Content-length was too short for trial version pages. Fixed.
- Shell and Start macros v1.650
They no longer use the "working" message, and parameters are expanded automatically.
- Macro syntax v1.650
Blank lines are allowed. Lines that are just // are allowed. These types of lines
within a macro section no longer generate error list entries.
- Form to HTML Converter v1.650
Upgraded to version 1.04.
HREF Tools Corp., 300 B Street, Suite 215, Santa Rosa, CA 95401 USA