Web applications depend on accurate time keeping. Sessions are managed using a cookie, and the server sets a lifetime for that cookie based on what it thinks is the current time. The client then receives the cookie and acts on it based on its own clock. Additionally, the server will direct the client to store responses that it sends in a cache until a specified time.

The Xbasic Explorer is an extremely useful tool when you are writing code in the Code Editor, or experimenting with code in the Interactive window. It is a complete reference of all of the commands, functions, methods, properties and constants in the Xbasic language. It also shows you all of the current objects that exist, all global variables that you have created, and all Global Functions that you have defined.

Properties and methods in the SSLSocket class.

Traditionally, Application Server administrators provide service for multiple applications by using a single instance of the Application Server, placing each distinct application within a different subdirectory under the webroot.

Recalculates calc fields

Open an existing table in a new session.

The Session object is used to work with the server session. The *[xb:Session]* and *[xb:Context.Session]* object are the same and can be used interchangeably in Xbasic scripts running on both the Classic Application Server and Application Server for IIS. See [Context.Session] for a list of properties and methods for the *[xb:Session]* object.

Logs in a user to a specific page and sets the authentication cookie's lifetime.

By default, a web page will not display files located outside of the webroot folder structure. The advantage of this restriction is that it prevents unauthorized users from changing or damaging your data. But when you want to selectively use data outside of the webroot, there are two techniques for overcoming this limitation.