This information is for end users and developers of W*API plug-ins/CGIs and others familiar with WebSTAR. Use it as guide for resolving differences in the serving of your Web content under Web Ten vs. WebSTAR and as a starting point for reporting Web Ten incompatibilities with your plug-in's/CGI's operation.
Web Ten ignores the Macintosh file creator and type of the requested document when determining a handler for a URL. The Web Ten suffix mapping table has no entries for Macintosh creator/type.
Plug-in/ACGI W*API requests to change global server parameters are reflected in the active (in memory) Web Ten database, but are not changed in the permanent Web Ten database. Permanent changes to Web Ten settings are made using the Web Ten Administration Server.
Web Ten registers the " .admin " URL suffix for administration of plug-ins and the main server. Accessing the local URL " /pi_admin.admin " will invoke the Web Ten plug-in administrator with links to individual plug-in administration URLs and the Web Ten Administration Server.
Ironically, the plug-ins delivered with WebSTAR 2.X from StarNINE do not conform to the W*API specification. Functionality of these plug-ins cannot be assured under Web Ten ; however, copying the WebSTAR Settings file to the Web Ten server root folder may provide limited capability of WebSTAR plug-ins under Web Ten .
Plug-ins that attempt to install Apple Event handlers will not operate properly under Web Ten . Plug-ins should use the W*API Interprocess Communication Callbacks for sending Apple Events and receiving Apple Event replies.
Plug-ins/CGIs that run correctly when called from the default Web Ten server but fail when called from a Web Ten virtual host may be making incorrect assumptions about an underlying WebSTAR run-time environment. Some tips for developers on taking advantage of the W*API in a Web Ten environment can be found at http://www.tenon.com/products/webten/pluginvhost.html .