Starting with WebHub v2.023, the WebHub System is undergoing visible reorganization.A quick explanation for existing customers:
For many reasons, we are moving toward a new WebHub System design. Under this scheme, the Hub will always runs invisibly as a service. For a while we were shipping a file named HubNoGUI. As of v2.030, the concepts tested in "HubNoGUI" have moved into Hub.exe, and "HubNoGUI" is history. From now on, the shipping Hub.exe runs only as a service and never has a GUI.
So how do you edit W-HTML for the HubApp, or make configuration changes? You run the "WebHubAdmin" module. How to you monitor active traffic? The Connected and Requests panels have moved into a separate "WebHubView" module. This means lower overhead on your production server, and it opens up a path for HREF to provide more features soon.
What new customers need to know:
The WebHub help file HAS been updated. Prior to 03-Apr-2004, get the latest help file here:
The WebHub help file HAS been updated. Prior to 03-Apr-2004, get the latest help file here: whub-hlp.zip
What to Download
Just before trying the new "WebHub Runtime System" installer...
function IsProcessRunning(PID: DWord): Boolean;
This means that you may now add a session panel (lib\whSessio.pas) into your own application without running into any conflicts with the Hub.
In earlier versions, when the directory became unavailable, the temporary directory was used and that was stored as a permanent choice, making it annoying to switch back to the originally desired LAN location.
Directory availability is checked at most once every 2 minutes, unless there is an error saving the session file.
The panels in WebHubAdmin function as they did when they were inside Hub.exe. There are a few improvements to the menu; for example you can now File-Open an AppID to start editing a particular WebHub application's W-HTML files.
WebHubView will only work with a Hub where the versions match up.
[WEBHUB] EditTemplate=c:\program files\HREF Tools\WebHub\Wizard\Editor\ShortCut.txt
If you want to customize the OnUpload features or adjust the delay of runisa.dll as a workaround on Win2000 or WinXP, you will need to create your own WebHubRunner.cfg file in the directory with with runner. Here is a starter copy:
[comments] Set the FileUploadPath to any path on a local hard disk and make sure that there are sufficient permissions for files to be written to that path by the runisa.dll ISAPI runner. On Win2000 and WinXPPro, set the DelayReturnInMilliseconds to a number from 1 and 500, to prevent blank page errors in IE. [WebHubISAPIRunner] FileUploadPath=d:\AppsData\HTTP\scripts\upload DelayReturnInMilliseconds=1