IntraWeb Archive

XI: AllowMultipleSessionsPerUser

XI: AllowMultipleSessionsPerUser

Some developers require that their users are able to run several sessions of an IntraWeb application. One session per browser tab or window. XI eliminates tmURL and tmHidden which allowed this, but we’ve added a new property to the ServerController which will allow this with cookie based sessions, yet still meet the other requirements of the new integrated page mode.

The ServerController contains a new property called AllowMultipleSessionsPerUser. It defaults to false, which causes IntraWeb applications to run as previous versions did using the tmCookie option. When set to false, the URL root will be:

http://iporname:port/

for example

http://127.0.0.1:4554/

If AllowMultipleSessionsPerUser is set to true, on each session start the user will be redirected to:

http://iporname:port/SessionID/

for example

http://127.0.0.1:4554/SessionID/

However a cookie will still be issued to the browser, however it will have its path set to /SessionID. IntraWeb will completley ignore the SessionID in the URL, and will still rely on the cookie value. However by creating unique paths, and assigning the cookies to the path instead of just the domain, this allows multiple IntraWeb sessions to be used by a single user in multiple tabs or windows.

Note that the SessionID is used in the URL merely for convenience and could be any unique identifier. Since it is ignored by IntraWeb, it may change in the future to be something other than the session ID, yet unique per user. Developers must not rely on this part of the URL and instead must continue to rely on the SessionID available in code, or in the cookie if accessed from browser side code such as Javascript.