IntraWeb Archive

XI: Start and Exec URLs

XI: Start and Exec URLs

A few small, but important change have been made for IntraWeb XI to allow implementation of planned future features.

What features?

We are planning an integrated page mode which will also allow serving of static content. This feature is planned for XII, however parts of it may appear in XI as well. For more inforation on the new URLspace, please see XI: URL structure.

Exec URL

In previous versions of IntraWeb, an execute URL was signified by /EXEC, and possibly followed by a session ID depending on the tracking mode. For example:

http://127.0.0.1:25710/EXEC

In XI, this format is deprecated and any URL that maps valid IntraWeb content will be considered an execute URL. Until the new page features are implemented, the only URL is the root URL. For the example above, it would change to:

http://127.0.0.1:25710/$

Resync Warnings

The display of resync warnings has been eliminated from XI. They may resurface in another form at a later time.

Start URL

XI no requires a separate start URL. Any URL that is recognized as an executable URL will suffice. Execute URLs will look for a session identifier, and if none is found a new session will be created automatically. In most cases the following can serve as a start URL:

http://127.0.0.1:25710/$

Root URL

The root URL http://127.0.0.1 is a special URL. If a content file exists in the root named index.html, it will be served. In such cases the exec or force start URL must be used. If no root index.html file exists, then the root URL will be treated as an exec URL, and thus also an implicit start URL when no session exists.

Force Start

In some cases you may wish to force create a new session, the explicit start url must still be used which is:

http://127.0.0.1:25710/$/Start

In previous versions this would create a new session and abandon the old session but leave it to time out. This was only of real relevance when tmCookie was used. In XI, the old session will not be abandoned, but instead will be explicitly destroyed. While this sounds like a drastic change in behaviour, this will likely not affect many users as the actual outcome is only different for users who were using tmCookie and explicit starts from an existing session.