Connection Events Test Options

The Connection Events Test dialog box tests sequences of events that require a reset of the terminal session: loading a model, connecting to the host, and establishing a client connection. The startup and shutdown sequences below illustrate the differences between each of the test options.

Dedicated Session: New Client

This option simulates the sequence of one client application disconnecting and another client connecting to this model using the Connect To Model method:

1. The Client Disconnected event is fired.
2. The terminal session navigates to the home entity, which could involve Execute Operation events.
3. The logout process is executed, which could involve firing the Execute Logout event.
4. The host session is disconnected from the host.
5. Steps 1-7 of standard reset processing are executed.
6. The host session is connected to the host.
7. The login process is executed, which could involve firing the Execute Login event.
8. The terminal session navigates to the home entity, which could involve Execute Operation events.
9. The Client Connected event is fired.

Steps 1-4 can also be accessed by pressing the logout button, while steps 5-9 can be accessed by pressing the login button on the same toolbar.

Pooled Session: New Session

The New Session option simulates destroying and creating a pooled session, then connecting to the session using ConnectToSession method.

With this option, a session pool host session is created, connected to the host, and logged in before a client session is actually created. This simulates the real-world behavior of a session pool session.

1. The Client Disconnected event is fired.
2. The terminal session navigates to the home entity, which could involve Execute Operation events.
3. The logout process is executed, which could involve firing the Execute Logout event.
4. The host session is disconnected from the host.
5. The Client Session Destroyed event is fired.
6. The Host Session Destroyed event is fired.
   
7. A Host Session Created event fires.
8. The login process is executed, which could involve firing the Execute Login event.
9. The terminal session navigates to the home entity, which could involve Execute Operation events.
10. The Client Connected event is fired.
11. The Authenticate User event is fired, with any resulting errors displayed in the Event Handler Console.
12. The Client Session Created event is fired.
    

Pooled Session: New Client

This option simulates the sequence of one client application disconnecting and another client reconnecting to this model using the ConnectToSession method.

In this case, only the client session events are fired because a session pool host session is not normally logged out or destroyed between client invocations.

1. The Client Disconnected event is fired.
2. The terminal session is navigated home, which could involve Execute Operation events.
3. The Client Session Destroyed event is fired
4. An Authenticate User event is fired.
5. The Client Session Created event is fired.
6. The Client Connected event is fired.
   

© 1999-2007 Attachmate Corporation. All rights reserved. Terms of Use.