Sessions and terminals configured for binding in an extensible manner

• US 20060195586A1
• Filed: 02/25/2005
• Published: 08/31/2006
• Est. Priority Date: 02/25/2005
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hagiu, Costin, Patwardhan, Makarand V., Sampath, Sriram, Stoyanov, Vladimir K., Bernardi, Ara, Parsons, John E. Jr.
• Application Number:
  US11/067,296
• Publication Number:
  US 20060195586A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

Systems and methods for configuring sessions and terminals for binding in an extensible manner are disclosed. In one implementation, a terminal is created in response to notification of an incoming connection. A session is also created. The terminal and session are bound together for operation. This implementation may be instantiated as computer-executable instructions defined on a computer-readable media.

Claims

1. One or more computer-readable media comprising computer-executable instructions for creating sessions and terminals for binding in an extensible manner, the computer-executable instructions comprising instructions for:

creating a terminal in response to notification of an incoming connection;

creating a session; and

binding the session to the terminal.

2. The one or more computer-readable media of claim 1, wherein creating the terminal comprises instructions for:

creating the terminal independently of creating the session with which the terminal is to be bound.

3. The one or more computer-readable media of claim 1, wherein creating the terminal comprises instructions for:

creating the terminal using a connection manager configured to create the terminal according to requirements indicated by the incoming connection;

wherein the connection manager is configured as a plug-in to a session manager; and

wherein the session manager creating the session and is a separate process from the connection manager.

4. The one or more computer-readable media of claim 1, wherein notification of the incoming connection is facilitated by instructions for:

operating a notification framework configured according to an event-based model wherein an appropriate connection manager is called to create a terminal type as indicated by the notification.

5. The one or more computer-readable media of claim 1:

wherein instructions for creating the terminal and for creating the session are configured in separate processes; and

wherein either of the separate processes may be modified or replaced to create a different terminal or session, without revision of the other process.

6. The one or more computer-readable media of claim 1, wherein creating the session comprises instructions for:

utilizing an API to communicate from a connection manager configured to create the terminal to a session manager configured to create the session, to request creation of the session.

7. The one or more computer-readable media of claim 1, additionally comprising instructions for:

creating a second session; and

rendering the session and the second session on the terminal simultaneously.

8. The one or more computer-readable media of claim 7, additionally comprising instructions for:

creating the session and the second session to have different security contexts and permission to access to different resources.

9. The one or more computer-readable media of claim 1, additionally comprising instructions for:

notifying one or more connection managers of events through an extensible framework, wherein the one or more connection managers are configured as plug-ins to a session manager and wherein the terminal was created by one of the one or more connection managers; and

communicating information from the one or more connection managers to the session manager using APIs, wherein the session manager created the session.

10. One or more computer-readable media comprising computer-executable instructions for implementing an architecture to create and bind sessions and terminals, the computer-executable instructions comprising instructions for:

creating a terminal in response to notification by a protocol;

creating a session for use with the terminal;

binding the session to the terminal; and

wherein creating the terminal and creating the session are performed by different processes.

11. The one or more computer-readable media of claim 10, wherein creating the terminal comprises instructions for:

selecting an appropriate connection manager based on a desired terminal; and

wherein the selected connection manager is configured as an extension to a session manager that created the session.

12. The one or more computer-readable media of claim 10, wherein the protocol comprises instructions for implementing a notification framework configured to allow extensions to receive notification of events.

13. The one or more computer-readable media of claim 10, wherein creating the session for use with the terminal comprises instructions for:

creating the session with a session manager in response to an API sent by a connection manager that created the terminal.

14. The one or more computer-readable media of claim 10, wherein binding the session to the terminal comprises instructions for:

acquiring by the session of I/O devices from the terminal.

15. The one or more computer-readable media of claim 10, additionally comprising instructions for:

disconnecting the session from the terminal;

creating a second terminal; and

binding the session to the second terminal.

16. An architecture configured to create sessions and terminals for binding in an extensible manner, comprising:

a session manager to create sessions;

a connection manager to create terminals and to bind a session created by the session manager to a terminal created by the connection manager; and

a notification framework to notify the connection manager of events.

17. The architecture of claim 16, wherein:

the session manager and the connection manager are separately defined processes; and

wherein the connection manager and session manager may be independently altered to result in creation of a different session type or terminal type, respectively.

18. The architecture of claim 16, wherein the session manager comprises:

a subsystem to which extensions may be connected; and

wherein extensions may be connected to, and disconnected from, the subsystem without requiring recompilation of the session manager.

19. The architecture of claim 16, additionally comprising:

a plug-in structure communicating with the session manager and configured to allow out-of-process execution of plug-ins; and

wherein the connection manager is configured as a plug-in compatible with the plug-in structure.

20. The architecture of claim 16, wherein selection of an appropriate connection manager of may be made to result in creation of a desired terminal, and wherein the session and the desired terminal may be bound to create a custom environment.