JP5023082B2 - Pushing asynchronous messages to web browsers - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a secure and scalable method to allow a web server to asynchronously push a message to a web browser. <P>SOLUTION: A method and a system for controlling a user interface presented by a web browser (104A) is provided. The web browser (104A) is not blocked and waits for the asynchronous message. The web browser (104A) presents a user interface and presents a user interface change in response to the reception of the asynchronous message. <P>COPYRIGHT: (C)2009,JPO&amp;INPIT

Description

  The present invention relates to communication over the Internet. More particularly, it relates to a user interface controlled by pushing messages asynchronously to a web browser.

  The Internet operates under a client / server model of information transfer. In such a model, a server on which information exists and a client computer are connected. Clients rely on servers for information transfer. In fact, the client is requesting server services. This service includes searching for information and sending information to the client when a database accessible by the server is queried. Another embodiment of these services is web page transmission from a server on the World Wide Web, which will be referred to as a “web server”, and send / receive mail processing. Internet users connect to a server computer and request server resource usage.

  Typically, the client computer is a local personal computer, and the server computer (host) is a higher performance computer that stores data and another computer system that stores the data. Have access to. The connection to the server is made via TCP / IP based on a telephone line, a local area network (LAN), or a wide area network on the Internet. For the web, web browser software such as Microsoft Internet Explorer running on the client computer is the client / server environment. A server in a client / server relationship is typically web server software, such as Microsoft Internet Information Server (MIS), which runs on a server computer. Because of the client / server relationship, many clients can access the same applications and files stored on the server.

  Typical communications on the web include a web browser that sends a request for a specific web page to a web server, and a web server that processes the request and sends a web page form response back to the web browser. including. Requests and responses are communicated using the hypertext transfer protocol (HTTP). HTTP is a web protocol that is included in the Transform Control Protocol / Internet Protocol (TCP / IP) for sending requests and responses.

  In general, communication in the network can be performed either synchronously or asynchronously. Here, synchronous means that the request side sends a message and blocks until the response returns, and asynchronous means that the request side sends a message and does not wait until the response returns. The term “synchronous” means here that the requester or web browser is blocked while waiting for a response to an HTTP request, and the term “asynchronous” means that the web browser has received a response to an HTTP request. Indicates that it is not blocked even though it is not. When a response to an asynchronous request arrives, the request side is notified by the transmission side that the response is ready, and can select whether to receive the response.

  Since the web browser is designed with high security, it receives information from the web server with strict synchronization rules. In web connection, a TCP / IP connection to the Internet is established when the user's web browser is started. An HTTP connection is established when a web browser requests a web page from a web server. The HTTP connection between the client and the server is continued only while information is actually exchanged. Therefore, when the web page is transferred from the web server, the HTTP connection between the server computer and the client computer is blocked. Even though the HTTP connection is blocked, the user of the web browser remains connected to the Internet via the TCP / IP connection.

  The client / server model allows a client computer to connect to a host server residing in the Internet and launch web browser software to search the web, perform searches and modify functions. Basically, in the client / server model, the web is provided on thousands of host computers that can be fully accessed by multiple personal computers running a web browser, an infinitely large file storage medium or database To be able to function as.

  Since the Internet works under the conditions of a client / server model, the client's web browser is designed to request information from the web server and receive information. If the client's web browser does not receive a response from the web server in a relatively short time, such as a few minutes, the attempt to establish an HTTP connection may be interrupted. Since the web browser is blocked, the web server cannot do anything else while waiting for a response from the web server. At the same time, the web server attempts to send a response to the web browser, and if the HTTP connection is lost, the attempt to send can be interrupted after a relatively short period of time. Therefore, web browsers are not set to wait indefinitely for responses, but rather are designed to receive web pages almost instantly than web servers.

  However, it may be desirable for the server to be able to “push” information to the client. For example, it is sometimes used by the Internet to wipe out information to individuals using a technique known as push technology. With push technology, data is automatically sent to the client computer system based on predetermined time intervals or specific event occurrences. These specific events may include automatic information generation requests, i.e. automated pulls, and Internet users automatically receive specific information that does not include each user request over time.

  Internet users typically subscribe to services that provide push technology to receive specific types of information. Websites that provide push technology are referred to as “channels” and typically provide information within a particular area of interest through a channel. The channel source collects information and provides the information to the subscriber at an automatic time interval specified by the subscriber.

  Such subscription channels are typically implemented to have subscription software downloaded to the subscriber's computer. Subscription software programs run regularly at specific time intervals, request web pages of interest and perform checks for updates in the channel. Updates may be stored on the computer hard disk drive of the client performing the request, and the user may view the information later without being logged on to the Internet. .

  Web browsers are initially designed not to access web pages or data unless the web browser requests a web page. By operating in a client / server synchronous request / response model, a web page or data that a user does not need, such as "spamming" being very destructive to the machine itself or a user session on the client computer. The file is not received. A subscription channel may remove this limitation by being acquired before the user-approval is reached and may execute the request on behalf of the subscriber user at specific intervals. However, the subscription channel may require additional software to be installed on the client computer system.

  With the widespread use of the Internet, many companies have been working hard to develop software that runs in a standard software browser and avoids the need for additional software to be installed on the client computer system. . For example, in a large customer support organization, it is desirable that the customer support provider should be able to access the application from their home computer, for example, to travel to other areas where travel is not available for dedicated application software. It should be accessible. However, a web browser is basically designed to request and display a web page, and is not designed to perform advanced mutual communication with a server. Therefore, providing a complicated user interface has been limited to providing highly functional client software. Under multiple conditions, it is desirable for the web server to be able to push information asynchronously to a web browser that supports an application, such as a customer support application, without using a web browser that first requests a web page . The term “asynchronous message” here refers to a message sent by a web server, which is not a synchronous response to a web browser request for a web page, but is blocked while the web browser waits for a message. Absent. An example situation where such asynchronous message push is desirable is when an event occurs to which the user should be notified instantly. The web server may perform event notification to the merchant when urgent help is needed, and even when the merchant is not currently accessing a particular website.

  It is difficult to realize that a web server performs an asynchronous message push without requiring an application program that must be installed on the client computer system. If the subscription channel runs the browser page client perfectly, the subscription channel provides updates to the user only when logging on to the subscription website and does not provide updates at specific time intervals. The user may have to log on to the website to receive updates. Only when the user is continuously connected to the subscription service website, the instantaneous update is reliably received. In order to provide services to many subscribers, it is unlikely that the subscriber service side will provide a sufficient continuous connection state. This solution is not scalable.

  Another solution is to have a program, such as a Java applet, that creates a listening thread on a portion of the client computer system, so that the web server pushes the information at the appropriate time at any time. Can do. However, the port is more likely to receive messages from any application that senses the port than the web server. This solution carries security risks. In addition, the web server must remember all clients, and messages are pushed to the correct client. The web server must initiate a connection to the appropriate port in order to push asynchronous messages to the corresponding client.

  Yet another solution is that the web browser continuously polls the web server to inquire which web server has the message to be communicated to the web browser. However, this solution is still not scalable. For example, a customer support application having thousands of customer support vendors sending a constant poll request may overload the web server. Web servers may be an obstacle for not being able to service appropriate requests.

  What is needed is a secure and scalable way to allow web servers to push messages asynchronously to web browsers. In order for the web browser to be able to perform other tasks, it is desirable not to be blocked in order to receive information from the web. It is also desirable that the web browser be protected from receiving unnecessary messages.

US Pat. No. 6,199,104 US Pat. No. 5,964,836

  The present invention provides a method and system for controlling a user interface displayed by a web browser.

  According to one aspect of the invention, a method includes controlling a user interface displayed by a web browser. The method further includes causing the web server to push an asynchronous message to the web browser, wherein the web browser indicates a change in user interface in response to the asynchronous message.

  According to another aspect of the invention, a method includes controlling a user interface displayed by a web browser by registering a web browser that is available to receive asynchronous messages. The web browser is not blocked while waiting for the asynchronous message. The method further includes causing the web server to push an asynchronous message to the web browser, wherein the web browser is responsive to the asynchronous message and the user interface changes.

  In yet another aspect of the invention, the method includes controlling the user interface displayed by the web browser by causing the web browser to provide a weight request to the web server, wherein the weight request is associated with the web browser. The method further includes the steps of identifying the source of the asynchronous message and associating the source with the weight request, wherein the associating step recognizes the web browser as a recipient of the asynchronous message. . The method further includes the step of pushing an asynchronous message to the web browser, wherein the browser displays the user interface change in response to the asynchronous message.

  A computer system, a computer program product, and a system for implementing the methods as described above are provided.

  The foregoing is a summary and, of course, the detailed description has been simplified, generalized and omitted, and those skilled in the art will appreciate that the present invention is not limited thereto. Other aspects, inventive steps, and advantages of the present invention, which are set forth only by the claims, are not limited to the detailed description set forth below.

The figure is a diagram of an embodiment of a client / server system to which a method in which an asynchronous message is pushed to a browser is applied. The figure shows the central component with the push of asynchronous messages to the web browser client. The figure is a flowchart showing asynchronous message push to the web browser client of FIG. The figure is a more detailed diagram showing the communication infrastructure in the embodiment of the client / server system of FIG. The figure shows the operation of the client / server system of FIG. 1 when executing the asynchronous message receive preparation process in the flowchart of FIG. The figure shows the operation of the client / server system of FIG. 1 when executing the asynchronous message receive preparation process in the flowchart of FIG. The figure shows the operation of the client / server system of FIG. 1 when executing the asynchronous message push process in the flowchart of FIG. The figure shows the operation of the client / server system of FIG. 1 when executing the asynchronous message push process in the flowchart of FIG.

  The following description is a detailed description of examples of the present invention and is not intended to limit the present invention. Rather, multiple alternative embodiments are encompassed by the claimed invention.

  In the following description, for the purposes of explanation, a number of specific embodiments are disclosed for the purpose of providing a thorough understanding of the present invention. However, one of ordinary skill in the art will practice the invention in a manner other than the specific embodiments. It is obvious that it can.

  A reference in “one embodiment” or “an embodiment” means that the particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. The phrase “in one embodiment” in the specification is not all references to the same embodiment, and is an independent embodiment, ie, an alternative embodiment, that excludes other embodiments from each other. Not all are referenced to the examples. Furthermore, various features are described which are shown by way of example and not by another example. Similarly, various different conditions may be described that may be used for multiple embodiments, but not used in other embodiments.

  FIG. 1 is a diagram illustrating an example of a client / server system 100 that enables a merchant to respond to customer support requests and / or information requests via multiple communication channels of different media types. . The client / server system 100 is a parent application of the present application, 09/09 filed on March 31, 2001, named “User Interface for Multi-Channel Communication” by Mingte Chen, Anil K. Annadata, and Kuang Huang et al. 823,531 (attorney disk number M-11518US, applicant reference number SIEB062 / US). The client / server system 100 is an embodiment of a system that executes asynchronous push of a message from a web server to a web browser, but the present application is not limited thereto. The ability to push messages asynchronously to a web browser is also applicable to multiple software applications that are accessible via the Internet.

  The client / server system 100 allows asynchronous messages to be sent to the web browser client 104A for the purpose of controlling the toolbar 105 that provides a user interface for use by merchants that support customers. Asynchronous messages notify the client of the arrival of communication via one or more communication channels. The client / server system 100 supports a plurality of communication channels with different media types. These media types include, but are not limited to, telephone, e-mail, fax, web collaboration, internet call me now, internet call me later, web chat, wireless Access protocols, paging, short message services, etc. are included.

  In the parent application, three types of clients 104 are disclosed: a web browser client 104A, a thin client 104B, and a dedicated client 104C. Since the client / server system 100 can operate only with a web browser as a client, the present invention is limited to the web browser client 104A in terms of applications.

  Web browser client 104A includes a web browser program such as Microsoft Internet Explorer that runs on the client's computer system (not shown). Web browser client 104A communicates with web server 188 and receives messages pushed asynchronously from web server 188 to web browser client 104A. Web browser client 104A has the ability to download instructions such as Java applets from a web server, such as web server 188, and executes the instructions.

  The application server 126 in the client / server system 100 functions for information to the web browser client 104A and transmits information through the web server 188. Here, the web server provides web page and other user interface changes for the web browser client 104A for display.

  Web browser client 104A is shown having a toolbar 105. Those skilled in the art will appreciate that other user interfaces providing toolbar functionality are available without departing from the spirit of the present application. The toolbar 105 is shown as part of the user interface via the web browser client 104A.

  The communication server 109 includes a session mode communication server 110, a request mode communication server 140, and an inbound communication receiver 170. Each communication server 110, 140, and 170 may have the ability to push messages asynchronously. However, since the session mode communication server 110 controls the user interface indicated by the web browser client 104A, this application will be limited to the functions of the session mode communication server 110.

  Further, although illustrated herein is an asynchronous message for communication over the phone that, in some embodiments, notifies the user of an incoming call, this application is any type of asynchronous related to either communication or non-communication. Messages can also be supported.

  A merchant using the web browser client 104A (herein treated as a user) logs into the client / server system 100 by accessing a corporate web page via the web server 188. A session is established for the merchant and is sent and received through at least one communication channel 130.

  A session is a logical connection from a web server 188 that is directed to a separate business process server, referred to herein as an object manager server 107. The object manager server 107 provides access to business objects and business logic. The business processing server determines when an asynchronous push of the message to the web browser client 104A is made. In the client / server system 100 described herein, the object manager server 107 then makes this logical connection by connecting to one or more additional servers that provide specific business functions, such as a session mode communication server 110. It may be expanded. The session will be described in detail in FIG. 5 and FIG.

  In the client / server system 100, the session mode communication server 110 allows the merchant to have different media types, eg, communication channels 130A, 130B, 130C, and so on using a single user interface provided via the web browser client 104A, Communication is enabled via a communication channel 130 such as 130D. To establish this communication, channel drivers 120, such as channel drivers 120A, 120B, and 120C, provide media specific communication via communication API 125. The communication API 125 enables the session mode communication server 110 to operate regardless of the media type and specific protocol of the communication channel.

  The three-tiered architecture of the web browser client 104A, web server 188, and business processing server (object manager server 107) allows the web server 188 to process web page requests and to another component of the client / server system 100. And offload business logic. Importantly, the functions provided by the servers such as the object manager server 107, the communication server 109, and the session mode communication server 110 may be implemented on a single server computer system or via multiple server computer systems. Note that it may be delivered as well. Furthermore, typically a large enterprise has a fully specialized computer system only to perform the functions of the web server 188, and owns a web server similar to multiple web servers 188. Nevertheless, the servers may reside on the same computer system, such as web server 188.

  In some embodiments, the application server 126 of the client / server system 100 may include an object manager server 107, a session mode communication server 110, a request mode communication server 140, an inbound communication receiver 170, a universal, as shown in FIG. A queue (UQ) system 102, a UQ business service 106, a web server 188, a web server 146, an enterprise application interface (EAI) object manager server 190, and a workflow process 144 are included. In some embodiments, communication between components in the application server 126 may include a suitable internal processing communication protocol related to a communication protocol such as transfer control protocol / Internet protocol (TCP / IP) known in the art. It can be realized using. These components and the interactions between them are as detailed in the parent application and related applications which are incorporated herein by reference.

FIG. 2 shows a three-tier architecture for performing an asynchronous push to a web browser. The business processing server 202 is a source of asynchronous messages. In operation 2 -1, business processing server 202 has to push the asynchronous message to the web server 188, the fact is indicated by operation 2-2 for Java (registered trademark) applet 116. Here, the web server 188 includes Microsoft's Internet Information Server (IIS), or standard off-the-shelf web server software such as Apache. In operation 2-3 , a Java (registered trademark) applet 116 controls the user interface as displayed by the web browser client 104A. In one embodiment, Java applet 116 controls a toolbar that allows merchants to communicate over a plurality of different media type communication channels.

  FIG. 3 is a flowchart illustrating an embodiment of a method for pushing an asynchronous message to a web browser client. In a communication connection setup step 310, a communication connection is established between the web browser, the web server, and the business processing server. Here, the business processing server can respond to determine that the asynchronous message should be pushed to the web browser. In order to push asynchronous messages, these communication connections establish that the business processing server can always communicate with the web server and web browser client.

  In an asynchronous message reception preparation step 320, the web browser client is registered with the business processing server to indicate that the asynchronous message can be received. In an asynchronous message push step 333, the asynchronous message is pushed to the web browser client. The asynchronous message reception preparation step 320 is described in detail in FIG. 5, and the asynchronous message push step is described in detail in FIG.

Communication Infrastructure FIG. 4 illustrates the results of performing a process 310 for setting up a communication connection for the embodiment of the invention illustrated in FIG. The components of FIG. 4 include a web browser client 104A, a web server 188 that communicates directly with the web browser client 104A, and two business processing servers, the object manager server 107 and the session mode communication server 110. Although the present invention can be performed by one business processing server, with respect to the client / server system 100 of FIG. 1, two business processing servers are used to illustrate the operation of the present invention. In order to indicate a communication connection in relation to the present invention, the Java® applet 116 causes the web browser client 104A to send a wait request 210 as part of a normal HTTP request to the web server 188. Eventually, through a communication in full la structure shown in FIG. 4, the asynchronous messages 290 are sent asynchronously to web browser client 104A from the web server 188.

  Referring to web server 188, web engine plug-in 185, such as Microsoft Internet Information Server (IIS), is used to communicate with session manager 220, object manager server 107, and the rest of client / server system 100. Functionally using an off-the-shelf web server. The session mode communication server 110 issues an asynchronous message and is used to execute processing by using the object manager server 107 and push the asynchronous message to the web server 188. The web engine plug-in 185 pushes an asynchronous message from the web server 188 to the web browser client 104A via the persistent HTTP connection 131. By causing the web server 188 to perform asynchronous message push, the user interface shown by the web browser client 104A is controlled.

  The session mode communication server 110 communicates with the web browser client 104A through a series of connections among the session mode communication server 110, the object manager server 107, and the web server 188. As described above, the session is a logical connection connected from the web server 188 to the object manager server 107. In this embodiment, for the web browser client 104A, an active connection 135A is used as a logical connection from the web server to the object manager server 107, which is the first business processing server. This logical connection is further extended to the second business processing server, session mode communication server 110, via a connection such as active connection 135B. It should be noted that a second connection is not required for the operation of the present invention, but is required for a specific purpose in the illustrated embodiment.

  In the embodiment of FIG. 4, active connection 135B establishes sub-connection 135B-1 between service request layer 235A and service request broker 230, and sub-connection 135B-2 between service request broker 230 and service request layer 235B. Including. Separating connections into sub-connections is characteristic of the particular embodiment shown and is not a requirement of the present invention.

A process corresponding to a specific web browser client 104A is executed on each session-related business processing server. In the embodiment shown, the session thread 16 0 users runs on object manager server 107, the communications server session thread 122 is executed on the session mode communication server 110. User session threads 16 0 and the communication server session thread 122 is described in more detail In the cross-reference of the aforementioned parent application. In the illustrated embodiment, the communication between the session threads 16 0 users with communication server session thread 122 is achieved by using a service request broker 230 via the active connection 135.

  The session mode communication server 110 maintains information of each connected client, here, the web browser client 104A. The session mode communication server 110 communicates interactively with the merchant by receiving incoming events such as customer support requests and pushing asynchronous messages to the user interface displayed to the merchant. Where possible, an incoming customer support request is generally the same as a customer support request received by the communication channel 130, with a brief interruption allowed for processing purposes only, and a transfer time for the customer support request. At the time, communicate with the merchant. This minimizes customer latency, especially for interactive requests to merchants.

  When an event such as an external telephone call (call) occurs, the user interface performs notification to the merchant using the interface change notification function to alert the merchant. For example, a notification function of the user interface may receive an asynchronous message, and may provide an operation command for flashing a button to notify a merchant of an incoming call. This notification function may also provide a display operation instruction for other information such as information about the caller (“screen pop”) until the merchant picks up the phone. When the merchant uses the toolbar 105 to receive, hold, or release, the user interface sends a command to the session mode communication server 110. Here, the server 110 communicates with one of the channel drivers 120 and sends a command to the communication channel that controls the telephone.

By having the function of a message it can be pushed asynchronously from the communication channel, skilled in the art will be able to receive the arrival work item, such as E- mail addressed to the skill in real time.

Session Manager As described above, a solution in which a web server can provide messages asynchronously to a web browser can enable a large-scale distribution application such as the client / server system 100 to support a large number of users. desirable. In general, a web server may satisfy the requests of multiple web browser clients, such as web browser client 104A. For example, each vendor using the client / server system 100 uses its own web browser client for accessing the web server 188. Next, the web server 188 performs communication with a business processing server such as the object manager server 107 on behalf of the web browser client. Each web browser client has a unique dedicated connection from the web server 188 to the business processing server where logically all communication of the web browser client is performed. These logical connections are called sessions and are managed by the session manager.

  Each session manager may have components that run on two servers, in this example session manager 220A running on web server 188 and session manager 220B running on object manager server 107. It is running. Session manager 220A and session manager 220B are collectively referred to as session manager 220. Since the two components of the session manager 220 perform processing by establishing a physical connection that exists between them, such as the active connection 135A, the processes on the two servers 188 and 107 can communicate with each other. Session manager 220A creates session manager listening thread 224 and follows active connection 135A. Session manager 220A maintains session-related local data as shown in session data 222A, and session manager 220B maintains local session data in session data 220B.

  Multiple active connections may be established between two servers. Referring to FIG. 2, active connection 135A shows one active connection between web server 188 and object manager server 107, and no additional active connections are shown. Since each web browser client may be idle for a significant amount of time, an active connection may not be established for each web browser client in order to conserve network resources and achieve scalability. The session manager allows active connections to be shared between web browser clients.

Whenever a component of the client / server system 100 needs to communicate, the component may call a corresponding session manager component on the same server system. Here, the server computer system determines an active connection capable of communication. For example, when the web engine plug-in 185 needs to send information for the user of the web browser client 104A, the web engine plug-in 185 requests the session manager 220A to send information. Session manager 220A determines a valid active connection for session manager 220B, such as active connection 135A, and sends information to session manager 220B via the active connection. Session manager 220B provides information, i.e., the user session threads 16 0 to the appropriate process corresponding to the web browser client 104A.

  A session manager, such as session manager 220, may convert the data to an appropriate internal process communication protocol, such a protocol being used in connection with a transfer protocol such as TCP / IP, for example. Used for communication between distribution components of the client / server system 100.

  Having a session manager such as session manager 220 and communicating on behalf of other components of client / server system 100 allows the logic associated with connections and sessions to be removed from components that perform other functions. And This simplifies the other components of the client / system 100 and avoids the complexity of session and connection management as part of the session manager 220.

  The merchant logs in to the client / system 100 by accessing the web page via the web server 188 and completing the login information. Various connections are established in response to login. Upon user login, session manager 220 establishes active connection 135A. When the communication client service 160 requests a connection to the session mode communication server 110, the service request broker 230 and the service request layers 235A and 235B establish an active connection 135B. When a connection to session mode communication server 110 is established, Java applet 116 establishes a persistent HTTP connection 131 between web browser client 104A and web server 188. In one embodiment, persistent HTTP connection 131 is a physical two-way socket connection from web server 188 to Java applet 116. The persistent HTTP connection 131 is dedicated to the web browser client 104A and allows the web server 188 to send asynchronous messages to the web browser client 104A at any time. In the embodiment as shown in FIG. 4, these connections allow asynchronous messages to be pushed, but active connection 135B is not required in this application.

  Active connections 135A and 135B remain active regardless of whether web browser client 104A is idle or not. Those connections may be closed when the user selects logout. These connections may be terminated after the web browser client 104A has been idle for some time, eg, 30 minutes. If the user has not used the web browser client 104 for a period of time, the session manager 220 may make a determination that the user is already unavailable.

Preparation for Receiving Asynchronous Messages FIG. 5 illustrates the preparation process for receiving asynchronous messages.

In action 5-1, the Java applet 116 sends a wait request 210 to the web server 188 to the web browser client 104A to indicate that the web browser client 104A can receive the asynchronous message. To send. The wait request 210 may correspond to a URL as shown in FIG.
http: //webserver188/.../start.swe? waitrequest = 1 & target = 160 & Session_ID = 104A_ID
It is indicated.

  A path element that is a part of the URL preceding the question mark (?) Indicates a directory path name for the web server 188. The URL search element, which is part of the URL following the question mark, provides parameters and values as name / value pairs.

  In this example, the first name / value pair, wait request parameter 212 indicates that the command should be executed by web engine plug-in 185. The target parameter 214 indicates the target process 160 corresponding to the communication client service 160, from which an asynchronous message may be received. The Java applet 116 accesses the target process information because the session corresponding to the web browser client 104A has already been established as a result of the setup communication channel step 310 of FIG. The session_ID parameter 216 indicates the session_ID of the session. The session_ID allows the web server 188 to push asynchronous messages to the corresponding web browser client, since the session is logically “dedicated” to satisfy a particular web browser client 104A request. And Other embodiments of the present invention may provide different parameters within the URL.

  The Java applet 116 allows the web browser client 104A to send a wait request 210 in HTTP format, which results in a “timeout” as in the case of a standard web browser URL request. "Do not cause. Despite not being immediately provided with a synchronous response, the web browser client 104A is not blocked by the response latency. The Java applet 116 continues to wait indefinitely for asynchronous messages from the web server 188, and the web browser client 104A is released to perform other tasks such as user interface control.

  In some embodiments, the web server 188 recognizes the “.swe” extension 211 of some path elements in the URL that precede the question mark (?). From the “.swe” extension 211, the web server 188 determines that the web engine plug-in 185 may handle the request. Web server 188 provides information provided in wait request 210 such as target parameter 214 and session_ID parameter 216 for web engine plug-in 185 in operation 5-2.

  In operation 5-3, the web engine plug-in 185 stores information from the wait request 210 in the request object 510. Here, the request object 510 is stored in the memory until the asynchronous message of the web browser client 104A is received. Request object 510 saves request information that may be required for pushing asynchronous messages to Java applet 116. Here, the Java (registered trademark) applet 116 uses an asynchronous message for the purpose of controlling the user interface displayed on the web browser client 104A. For example, this information may include a username and / or other identification information for the web browser client 104A. Optionally, the web engine plug-in 185 may return a “request pending” status (not shown) to the Java applet 116. The request object 510 remains in memory and is used when the session manager 220A detects that an asynchronous message has arrived via the session manager listening thread 224.

  The web engine plug-in 185 generates a callback object 530 for the wait request 210 from the request object 510 and places the callback object 530 in the client waiting list 550. The callback object 530 provides context information that is used when an asynchronous message is received for the web browser client 104A. The client waiting list 550 provides all client lists, such as the web browser client 104A, where all clients can receive asynchronous messages.

  In operation 5-4, when the web engine plug-in 185 calls the session manager 220A and calls a wait request, a reference to a callback function to be called when an asynchronous message is received for a wait request, and a callback function. Provides a reference to the context information to be used for In this embodiment, a reference to callback function 540 and callback object 530 is provided. In FIG. 4, only a single type of callback function is disclosed, but multiple for different types of asynchronous messages, different types of events, or other situations that require special handling without departing from the spirit of the present application. The callback function may be included.

  Session manager 220 assigns request_ID, which is a unique identifier for each request. The session manager 220 also stores a request_ID column 222A-1, which is a unique identifier in the session data 222A, along with information needed when an asynchronous message is received for the web browser client 104A. In the example shown in FIG. 5, the unique identifier request_ID has a value of 104A_ID / 1, indicating that it is the first request from the web browser client 104A. Session manager 220A also stores a reference to the callback function in callback column 222A-2 in the case of pointer 540p. Session manager 220A also stores a reference to context information in context column 222A-3, pointer 530p, for use when invoking a callback function. In this case, the context information to be used is stored in the callback object 530. In another embodiment, rather than a store reference for callback function and context information, session manager 220A may store voice callback function and context information in session data 222A.

In operation 5-5, the session manager 220 </ b> A sends a request including the request_ID and other information values such as the value of the target parameter 214 from the wait request 210 to the session manager 220 </ b> B inside the object manager server 107. To do. Session manager 220A, before being sent to session manager 220B, may command converts the request to the appropriate internal process communication protocol.

When receive a request from the session manager 220B, session manager 220B determines the corresponding process for handling requests. This Kodewa, Ru is a user session thread 16 0. Session manager 220B places the value of request_ID in session data 222B request_ID column 222B-1, and places an identifier for the handler in handler column 222B-2. Session manager 220B then places information from the request, such as the value of target 214 and the identifier of the handler, into request queue 560 at operation 5-6. Request queue 560 is a general request queue for all requests received by object manager server 107 for all users and all types of services. In the embodiment shown, includes a unique identifier request _ID for Request _ID column 562 is requested, the data column 564 includes a target parameter value 160, the handler column 566 for user session 16 0 Contains an identifier. When the object manager server 107 is in the idle state, the object manager server 107 retrieves a request from the request queue 560 in order to perform the processing as shown in operation 5-7.

When the object manager server 107 retrieves a request from the request queue 560, the object manager server 107 includes a process identifier for processing the request from the handler column 566. In operation 5-8, provides a request object manager server 107 to the user session threads 16 0, the user session threads 16 0 to weight map 570 in operation 5-9, are arranged information from the request. The weight map 570 also has a request_ID, which is a unique identifier for the request, in the request_ID column 572, and the identifier of the process from which an asynchronous message is expected (here, the communication client service 160) is the target column. 574 inside. Placing the request_ID in the weight map 570 is “recording” the web browser client 104A, where the web browser client 104A is unique to the request_ID as a client capable of receiving asynchronous messages. Associated with

Push diagram of asynchronous message to the web browser 6 shows the push asynchronous messages directed to the web browser from the object manager server 107 is a business process server. In order to disclose the ability to push asynchronous messages regarding the client / server system 100, the communication service 113, the OM listening thread 234, the active connection 135B-1, and the service request layer 235A are included. These components are not essential to the operation of the present invention, and other embodiments of the present invention may not include components that provide equivalent functionality. For example, all business logic functions may be included in a single type business processing server that performs a decision operation when all business logic functions are to be pushed an asynchronous message.

In this example, an asynchronous push is initiated by the arrival of an event, such as event 610, in OM listening thread 234 via active connection 135B-1. When event 610 is reached, service request layer 235A determines a handler process to process event 610. This process may be determined, for example, using the session ID provided for event 610 by service request broker 230 in FIG. In operation 6-1, the communication service 113 on the user session threads 16 within 0 is determined to be a process for handling an event 610, the service request layer 235A provides an event 610 to the communication service 113. In operation 6-2, the communication service 113 transmits the event 610 into the request queue 560 identified by the value in the request_ID column 562 of 610_ID, and in operation 6-3, the event in the handler column 566 is processed. The communication client service 160, which is the counterpart, is identified as the process. Data specifications for event 610 are provided in data column 564.

  In operation 6-4, the object manager server 107 collects the event 610 from the request queue 560 and provides the event 610 to the communication client service 160. The communication client server 160 accesses the target column 574 of the weight map 570 to determine which is the target for the request in the weight map 570. If the value 160 is found in the target column 574, the communication client service 160 uses the request_ID column 574 to determine the unique identifier request_ID of the request to which the event corresponds. The communication client service 160 determines an appropriate event response and generates an asynchronous message 290 for the purpose of including a request_ID and an instruction to execute the event response. For example, the event response may include blinking a button on the toolbar 105, generating a “screen pop” of data, or presenting a window to the front of the web browser client 104A. Good. Asynchronous message 290 includes an operation instruction for Java applet 116 and executes an event response.

  In operation 6-5, the communication client service 160 supplies an asynchronous message 290 to the session manager 220B and makes a request to the session manager 220B to send the asynchronous message 290.

  In act 6-6, session manager 220B provides asynchronous message 290 to session manager 220A. Session manager 220A first checks the client's waiting list 550 to notify that the client can receive the asynchronous message. Session manager 220A matches the request_ID value provided in asynchronous message 290 with the value in request_ID column 222A-1. In this 540 case, the session manager 220A determines a callback function to make a call and determines context information for providing the callback object 530.

  In action 6-7, session manager 220A provides callback object 530 to callback function 540. In action 6-8, the callback function 540 uses the request object 510 to determine the web browser client to which the asynchronous message is to be sent and pushes the asynchronous message to the web browser client.

  When Java applet 116 receives an asynchronous message, persistent connection 131 is closed. In order to enable the web browser client 104A to receive asynchronous messages, the Java applet 116 sends another wait request. The communication client service 160 continues communication with the Java (registered trademark) applet 116 and controls user interface changes displayed by the web browser client 104A.

  For example, when a user logs out by clicking a logout button on the toolbar 105, the session manager 220 cleans up the resources that the object manager server 107 has allocated for the web browser client. For example, the active connection 135B-1 to the service request broker 230 and the active connection 135B-2 to the session mode communication server 110 may be closed.

  As described here, asynchronous push from a web server to a web browser has many advantages, for example it provides data to the user in real time to a user with only a web browser It is possible to access a web-based application that controls the user interface. The web browser client is not blocked, and user interface changes are accomplished by instructions pushed asynchronously, without requiring a request to be made by the web browser client for each user interface change To change.

Other Embodiments The invention has been described with reference to software applications running on one or more computer systems. However, those skilled in the art can distribute the present invention as various types of program products, and the present invention does not depend on the specific type of signal bearing media used for actual distribution. You can see that it applies. Examples of media include recordable media such as flexible disks and CD-ROMs, transfer media such as digital and analog communication links, as well as all future media media and distribution systems.

  Moreover, in the foregoing detailed description, various embodiments of the invention have been presented using diagrams, flowcharts, and examples. Those skilled in the art will appreciate that each block diagram element, flowchart step, and / or operation and / or element shown through the use of the embodiments may be a wide variety of hardware, software, firmware, or any combination thereof. Etc., it will be understood that it can be realized individually and / or mutually. In one embodiment, the present invention may be implemented by an application specific IC (ASIC). However, one of ordinary skill in the art could similarly implement the embodiments described herein with a general purpose IC, such as a computer program, firmware, or combination thereof running on a computer in whole or in part. Please understand. In light of the detailed description of the present invention, it is possible for one skilled in the art to design a circuit configuration and / or write programming code for software or firmware.

  The invention is of course adapted to achieve the stated advantages, not to mention of its inherent nature. Although the invention has been described with reference to specific embodiments, it is not intended to limit the invention. The present invention includes modifications and changes relating to its form and function. The described embodiments are illustrative and do not limit the spirit of the invention. In other words, the scope of the right of the present invention is limited only by the scope of the claims, and includes all equivalents.

Claims (9)

A method for communication using a client / server system including an application server device including a web server and a client device including a web browser,
A control process for causing the application server device to control a user interface displayed by the web browser of the client device;
The control process is
In response to an incoming event, causing the web server to push an asynchronous message containing information indicating the arrival of communication from a communication channel to the web browser asynchronously with the arrival of the event;
Allowing the web server to identify the source in the application server device of the asynchronous message;
Causing the web server to provide a wait request associated with the web browser, wherein the wait request does not push data including an immediate response to a request from the web browser And the control process further includes:
The web server includes a process of associating the sender and the wait request, and the process of associating the value included in the wait request to a user session thread and a session manager listening thread corresponding to the sender. A recording process, wherein the control process further includes
Causing the web browser to display a change in user interface in response to the asynchronous message;
The process of providing a wait request to the web browser includes a request instruction according to a Java (registered trademark) applet for providing the wait request.
Downloading from a web server to the web browser, the method further comprising:
A method comprising causing the application server device to generate the asynchronous message .   The asynchronous message identifies the wait request, identifies the web browser as a recipient of the asynchronous message by the identification,
The method further comprises:
The method according to claim 1, further comprising: causing the application server device to provide the asynchronous message to the web server. The method further includes
A step of causing the application server device to store a reference to a callback function including information from the wait request;
Causing the application server device to use the reference to invoke the callback function when the asynchronous message is provided to the web server, wherein the callback function pushes the asynchronous message; The method of claim 2. The method further includes
The method according to claim 3, comprising causing the application server device to provide context information to the callback function, wherein the context information identifies the web browser. The method further includes
Assigning the wait request to the connection between the web server and the business processing server to the application server device;
The method according to claim 2, further comprising: causing the application server device to listen to the connection for the asynchronous message. The step of causing the web server to push the asynchronous message includes a step of calling a callback function associated with the web browser when the asynchronous message is received by the application server device. 6. A method according to any one of claims 1 to 5, wherein an asynchronous message is pushed. The method further includes
Storing the reference for the callback function in the application server device;
The method according to claim 6, further comprising: causing the application server device to use the reference to call the callback function. The method further includes
Causing the application server device to store a second reference for context information identifying the web browser;
The method according to claim 7, comprising causing the application server device to use the second reference to provide the context information to the callback function. The change in the user interface is
Moving the first user interface object to visually attract the user's attention;
The process of displaying a screen pop of data,
The method according to claim 1, comprising at least one of moving a web browser window to the front of the screen.