System supporting concurrent operation of multiple executable application operation sessions

• US 20040215703A1
• Filed: 02/04/2004
• Published: 10/28/2004
• Est. Priority Date: 02/18/2003
• Status: Abandoned Application

• Current Assignee: Siemens Medical Solutions Health Services Corporation (Siemens AG)
• Original Assignee: Siemens Medical Solutions Health Services Corporation (Siemens AG)
• Inventors: Haley, John D., Song, Xiping, Kaehn, Keith
• Application Number:
  US10/771,946
• Publication Number:
  US 20040215703A1
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: G06F 2209/5016 Session
• CPC Class Codes: G06F 9/5033 considering data affinity
• CPC Class Codes: G06F 9/505 considering the load

Abstract

According to one aspect of the present invention, a system, employing an application for supporting concurrent operation of multiple user initiated operation sessions, includes a communication processor and a processor. The communication processor communicates a session initiation request to a managing application to initiate generation of a session identifier particular to a user-initiated session. The communication processor receives from the managing application data representing a response address link identifying an address of a web page supporting the particular user initiated session. The data representing the response address link incorporates an identifier for identifying a particular server supporting the particular user initiated session. The processor parses the received data representing the response address link to extract and store the server identifier for use in directing communications associated with the particular user initiated session to the particular server.

Claims

1. A system employed by a first application for supporting concurrent operation of a plurality of user initiated operation sessions, comprising:

a communication processor for communicating a session initiation request to a managing application to initiate generation of a session identifier particular to a user initiated session and for receiving from said managing application data representing a response address link identifying an address of a web page supporting said particular user initiated session, said data representing said response address link incorporating an identifier for identifying a particular server supporting said particular user initiated session; and

a processor for parsing said received data representing said response address link to extract and store said server identifier for use in directing communications associated with said particular user initiated session to said particular server.

2. A system according to claim 1, wherein

said communication processor initiates communication associated with said particular user initiated session with said particular server using a URL incorporating data representing said particular server identifier.

3. A system according to claim 2, including

a switch for receiving and parsing said URL to detect said data representing said particular server identifier and for redirecting said communication associated with said particular user initiated session to said particular server.

4. A system according to claim 3, wherein

said switch detects said data representing said particular server identifier in response to predetermined rules and

said predetermined rules compare URL character strings with a predetermined character string to determine a match of a server identifier with stored predetermined server identifiers to identify a particular server.

5. A system according to claim 1, wherein

said processor for parsing said received response address link is implemented in at least one of, (a) JavaScript, (b) XML, (c) HTML, (d) another Script language and (e) another computer language.

6. A system according to claim 1, wherein

said session identifier is used to uniquely identify said user initiated session.

7. A system according to claim 1, wherein

said session initiation request to said managing application also initiates generation of an encryption key particular to said user initiated session for use by said first application.

8. A system according to claim 1, including

an entitlement processor for authorizing user access to said first application in response to validation of user identification information.

9. A system according to claim 1, wherein

said managing application manages operation of a server.

10. A system according to claim 1, wherein

said communication processor communicates said session initiation request to said managing application using a URL.

11. A system employed by a managing application for supporting concurrent operation of a plurality of user initiated application operation sessions, comprising:

a session identifier generator for generating a session identifier particular to a user initiated session in response to a received session initiation request; and

an interface processor for providing data representing a response address link identifying an address of a web page supporting said particular user initiated session, said response address link incorporating an identifier for identifying a particular server supporting said particular user initiated session.

12. A system according to claim 11, wherein

in response to receiving a URL address associated with said session initiation request,

said interface processor provides a redirected URL as said response address link comprising a redirected URL identifying an address of said web page supporting said particular user initiated session and incorporating an identifier for identifying a particular server supporting said particular user initiated session.

13. A system according to claim 11, including

a switch for receiving and parsing a URL to detect said data representing said particular server identifier and for redirecting said communication associated with said particular user initiated session to said particular server.

14. A system according to claim 13, wherein

said switch detects said data representing said particular server identifier in response to predetermined rules and

said predetermined rules compare URL character strings with a predetermined character string to determine a match of a server identifier with stored predetermined server identifiers to identify a particular server.

15. A system according to claim 11, wherein

said system is implemented in at least one of, (a) Microsoft Active Server Page (ASP) compatible language and (b) another computer language.

16. A network compatible system for distributing messages associated with a plurality of user initiated operation sessions of an executable application, comprising:

an interface processor for receiving data representing a URL associated with a request for data supporting a particular user initiated session; and

a switch processor for,

parsing said data representing said URL to identify data representing a server identifier,

comparing said server identifier with a plurality of stored predetermined server identifiers to identify a matching server identifier corresponding to a particular server and for redirecting said request for data supporting said particular user initiated session to said particular server in response to a match.

17. A system according to claim 16, wherein

said switch processor compares said server identifier with said plurality of stored predetermined server identifiers by comparing a character string of said server identifier with character strings of said plurality of stored predetermined server identifiers.

18. A network compatible system for distributing messages associated with a plurality of user initiated operation sessions of an executable application, comprising:

an interface processor for receiving data representing a URL associated with a request for data supporting a particular user initiated session; and

a switch processor for,

parsing said data representing said URL to identify whether said URL is associated with a data request of a first or different second type, and

processing said URL associated data request of a first type differently to a URL associated data request of a second type.

19. A system according to claim 18, wherein

said switch processor parses said data representing said URL to identify whether said URL associated data request is of a first type by determining if a URL data field identifies a server.

20. A system according to claim 19, wherein

said switch processor parses said data representing said URL to identify whether said URL associated data request is of a first type by determining if said URL data field contains an ASP extension.

21. A system according to claim 18, wherein

said switch processor parses said data representing said URL to identify whether said URL is stateless.

22. A system according to claim 21, wherein

said switch processor determines if said URL data field is stateless if it contains at least one of, (a) a .gif extension, (b) a .js extension (c) a .jpeg extension and (d) a .html extension.

23. A system according to claim 18, wherein

a URL associated data request of a first type is performable by a particular server and

a URL associated data request of a second type is performable by a plurality of different servers.

24. A system according to claim 23, wherein

if said URL is associated with a data request of a first type,

said switch processor compares said server identifier with a plurality of stored predetermined server identifiers to identify a matching server identifier corresponding to a particular server and for redirecting said request for data supporting said particular user initiated session to said particular server in response to a match.

25. A system according to claim 23, wherein

if said URL is associated with a data request of a second type,

said switch processor directs said request for data supporting said particular user initiated session to any one of said plurality of different servers.