Platform SDK: Web Telephony Engine |
A key difference between the WTE and graphical Web browsers is the concept of a session. The WTE supports sessions; graphical Web browsers do not.
In Web telephony, a session begins when TAPI offers a call to the WTE before the call is even answered. A session ends when an application calls the External.Abandon method, which typically occurs some time after the call has been disconnected.
The WTE creates a new instance of the Session object at the beginning of each session, and destroys the object when the session ends. The Session object is always available to the application, providing a convenient place for storing client-side variables and objects the application may need throughout the session. These objects can be TAPI objects, MAPI objects, or any others that run on the client side. You can also use the Session object to keep track of the call, the HTML pages that the caller has visited, variables that the application changed at run time, and so on. For more information, see The Session Object.