This is the greatest difference between the IIS and Windows Mobile implementations of ASP. Windows Mobile does not provide support for the Sessionor Applicationobjects and does not send the Session-ID cookie that is used on IIS. Therefore, there is no automatic technique for maintaining states between requests or sessions.

The script writer must maintain information between requests and sessions. A script writer can do this by sending cookies to the client browser. This scheme assumes that the client browser has cookie support enabled.

Windows Mobile ASP treats the <OBJECT> tag and properties as plain text. Interpretation of the <OBJECT> tag by the client browser is browser-specific. For more information, see Server Object Implementation.

None of the methods or properties that are associated with transactions is supported on Windows Mobile ASP. Tags and commands that are used by ASP on IIS to support transactions are ignored by Windows Mobile ASP and treated as plain text. How the client browser interprets these values is browser-specific.

There is no support for server-side scriptlets in Windows Mobile ASP. The <SCRIPTLET> tag and related tags are ignored by Windows Mobile ASP and treated as plain text. How the client browser interprets the <SCRIPTLET> tag is browser-specific.

On IIS, it is possible to specify options such as <SCRIPT LANGUAGE = JSCRIPT RUNAT = SERVER>, in which case the code between the <SCRIPT> and </SCRIPT> tags is executed on the server in the specified language, instead of on the client computer.

Windows Mobile ignores the RUNAT option of <SCRIPT> tags and sends the script to the client browser. How the client browser interprets the RUNAT option is browser-specific.

Windows Mobile ASP does not search automatically for a file that is named Global.asa to obtain global settings. Initial settings or commonly used routines may be included by using header files.

Script procedures may be named Application_OnStart, Application_OnEnd, Session_OnStart, or Session_OnEnd, although Windows Mobile ASP does not treat them differently from any other user-created procedures. Windows Mobile ASP does not call script procedures automatically on application or session initialization or on termination, as is the case with IIS-based ASP.

The Web Server does not provide metabase support. If a script contains a property that can be set in the IIS metabase, but that is not explicitly listed as supported in this Web Server document, it is not supported for use with the Web Server. For example, scripts containing ScriptMapstatements may operate correctly with IIS, but they will fail with the Web Server.