| Platform SDK: Web Telephony Engine |
A Session object can be used by an application to store variables and objects. The scope of the stored objects and variables is the entire session; that is, until the session terminates. No information is retained between sessions.
The session table supports strings, numbers, and objects. In the case of objects, you must use "Set" to retrieve the object, or call the methods directly. This is a read-write property, although it is actually implemented as a collection.
WTE follows COM concepts of handling object interfaces; that is, reference counting. For example, the engine calls the AddRef method to increment the reference count before returning any interface. Before exiting, the engine clears the table and releases all object interfaces.
Web telephony suggests the model of a client-side session mainly to ease the work of the author. The client-side session allows the author to keep client-side objects that are used in the telephony application. Unlike regular Internet Explorer objects, where objects live only in one page, these objects have a wider scope, up to the entire session. These objects can be TAPI objects, MAPI objects, and other objects that run in the Internet Explorer client side (inside Web telephony). The author can also use the session object to keep track of the call, the pages the caller visited, the variables changed by the application at run time, and more. Note that there are no security problems associated with the Session object because the caller cannot browse through arbitrary sites on the Internet.
LastVisitedPage, LastVisitedTagID, ServerName, SessionName, SessionState, Value
Windows NT/2000: Requires Windows 2000.
Windows 95/98: Unsupported.
Header: Declared in Mswtecom.idl and Mswtecom.h.
Library: Use Mswtecom.lib.