Objects manage the Application state and provide simple access to forms and HTTP parameters. They come in both built-in and installable shapes.

Objects are programming language components that provide tools for competing for basic repetitive programming tasks. Things often offer simple access to forms and manage the Application state. ASP objects come in built-in and installable shapes.

The Active Server Pages (ASP) framework provides six built-in objects you can use in scripts.

Server Object

The server object provides access to methods and properties on the server.

Application Object

You can use the application object to share information among all of the application’s users. The application is defined as all the .asp files in a virtual directory and its subdirectories. Because more than one user can share the application object, there are methods for locking and unlocking it to ensure that multiple users do not try to alter a property simultaneously.

Session Object

The session object stores information needed for a particular user session. Variables stored in the session object are not discarded when the user jumps between pages in the application; instead, these variables persist for the entire user session.

The Web server automatically creates a session object when a user who does not already have a session requests a Web page from the application.

The server destroys the session object when the session expires or is abandoned.
One everyday use for the session object is to store user preferences such as high, medium, or low graphics set on a previous visit to the Web applications. The session state is maintained only for browsers that support cookies.

Request Object

The request object retrieves the values the client browser passed to the server during an HTTP request.

Response Object

The response object sends the output to the client.

ObjectContext Object

The ObjectContext object is used to commit or abort a transaction initiated by an ASP script. The ObjectContext object provides information about the transactions and includes information about the client and the state of the client’s connection to the server. It permits the developer to avoid an expensive operation if the user has cancelled the page.