Transmitting information over a network

[0001] This application claims the benefit of Provisional Application No. 60/162,875, filed Nov. 1, 1999.

[0002] This invention relates to transmitting information over a network.

[0003] Network servers, such as web servers, normally receive requests for information from remote client computers over a network, such as the Internet or an intranet. For example, the requests for information may be HyperText Transfer Protocol (HTTP) “POST” or “GET” requests that are transmitted by a web browser on a client computer when a user submits a query to a web server. Network servers may transmit information to the client computer in response to the request. The transmitted information may be data such as a web page that is formatted in the HyperText Markup Language (HTML), promulgated by the World Wide Web Consortium (W3C). The transmitted information may also be an executable that is, for example, written in the JAVA™ programming language, by Sun Microsystems Inc. A JAVA™ interpreter on the client computer may execute such an executable.

[0004] It is sometimes necessary to transmit an executable to the client computer along with data that is to be processed on the client computer by the executable. For example, a web server may respond to a request for flight itineraries by sending the flight itinerary data along with a JAVA™ applet for graphically displaying the data.

[0005] A first general aspect of the invention relates to a method that includes transmitting information by transmitting an executable to a remote location over a network, generating data, and transmitting the generated data to the remote location over the network. At least part of the data is generated while the executable is being transmitted.

[0006] By generating part of the data while the executable is being transmitted, the method reduces the delay or latency before the executable and the data arrive at the remote location. The reduction in the delay makes the method more responsive to a user.

[0007] A second general aspect of the invention relates to an article that includes a machine-readable medium, which stores machine-executable instructions operable to cause a machine to perform the method of the first general aspect of the invention.

[0008] A third general aspect of the invention relates to an apparatus that includes a storage system that stores the executable and the instructions, and a server processor, which executes the instructions to perform the method of the first general aspect of the invention.

[0009] Embodiments of the invention may include one or more of the following features. A client at the remote location receives the transmitted executable and then later receives the generated data. The client includes a client processor that executes the executable and indicates that the client computer is waiting for the data. By receiving and executing the executable before the data is received, the client can inform the user that the client is waiting for the data, further increasing the responsiveness of the method to the user. When the data is received, the client processor executes the executable to process the data.

[0010] A first portion of the data is generated before a second portion of the data and at least part of the first portion of the data is transmitted while the second portion is being generated, further reducing the latency of the method. The client receives the first portion of the data before it receives the second portion of the data and the executable processes the first portion of the data before the second portion is received. The executable also causes the client to indicate that the first portion of the data has been received before the second portion is received, thereby further increasing the responsiveness of the client.

[0011] The information is transmitted in response to a request for information, while the data is transmitted to the client in response to a request for data separate from the request for information. A web page containing a directive to a web browser to request the executable is transmitted to the remote location and a request for the executable is later received from the web browser. The executable is transmitted to the remote location in response to the request for the executable.

[0012] Among other advantages of the invention, the reduction in latency and the improved responsiveness of the client improve the experience of the user.

[0013] The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.

[0019] Like reference symbols in the various drawings indicate like elements.

[0020] As shown in FIG. 1, a server 10 receives requests 12a, 12b for travel information 18 from remote client computers 14a, 14b over a network 16, such as the Internet or an intranet. As will be described in greater detail below, the server 10 may respond to a request 12 by transmitting travel data and a JAVA™ applet to the client over the network 16. The applet is executed on the client computer to process the travel data. The server 10 is configured to generate the travel data while transmitting the applet and then later transmit the travel data to the client computer, as will be described in greater detail below.

[0021] Server 10 includes a processor 22 and a network interface 20 that transmits information 18 and receives requests 12 from the network 16. The server 10 also includes a computer-readable storage subsystem 24 that stores computer programs, which are executed by processor 22. Storage subsystem 24 may include a memory, a CDROM, a floppy disk, a hard disk drive, a disk array, or a floppy disk. A multi-tasking operating system program 26 allows the server 10 to perform multiple tasks at the same time. A web server program 28 receives the requests 12 from a client computers 14a, 14b through the network interface 20 and responds to the requests by transmitting information 18 through the network interface 20 to the client computer. For example, web server 28 may send web pages 30 or a client executable 32, such as a JAVA™ applet, both of which may be stored in storage 28. Web server 28 may also respond to requests by using a travel program module 34 to generate travel data 36 from a travel database management system program (DBMS), and transmit the travel data through the network interface 20.

[0022] The travel module 34 is a computer program module, such as a dynamically linked library, that is invoked by the web server 28. Web server 28 uses the multi-tasking operating system 26 to invoke the travel module 34 while the web server 28 is still running. For example, web server 28 may invoke the travel module 34 as a separate operating system process or a separate thread.

[0023] The client computer 14a includes a network interface 39 and a storage subsystem 40 that stores client programs, such as a web browser 42 and a JAVA™ interpreter 44 that is associated with the web browser. Client computer 14a also includes a processor 46 that executes web browser 42 to receive input from a user through an input device 48 and transmit the input as requests 12a to the server 10 through the network interface 39. The input device 48 may be computer keyboard or a mouse associated with the client computer 14a. Web browser 42 also receives information 18 from server 10 through the network interface 39 and presents it to the user on a display 50 that is associated with the client computer 14a. When the information received includes client executable 32, web browser 42 invokes java interpreter 44 to execute the executable 32. Web browser 42 also stores the information 18 in a cache 52. Should the user later request the stored information 18, the web browser retrieves the information 18 from the cache 52 thereby eliminating the need to receive the information from the network 16. This makes the information available more quickly because the network 16 takes longer to transmit the information 18 than it takes to retrieve the information from the cache 52.

[0024] Referring to FIGS. 1 and 2, a user requests a search web page 30a for searching for travel itineraries, by typing a Uniform Resource Location (URL) 50 associated with the web page 30a into an URL input 52 associated with the web browser 42. The web browser transmits the request to the server 10 through the network 16 and the server 10 responds to the request by sending the web page 30a to the browser 42, which in turn presents the web page to the user on display 50.

[0025] A user enters search criteria for searching for travel itineraries including a point of departure, a departure time, a point of arrival and an arrival time into inputs 54a–54d contained within search web page 30a. The user then clicks on submission button 56, causing the browser 42 to generate an HTTP post request 12 and transmit the request to the server 10 over the network 16. Upon receiving the request, the server 10 transmits the client executable 32 to the browser 42 while generating the information 18 about the travel itineraries.

[0026] As shown in FIG. 3, the browser 42 presents a web page 30b while the browser waits for information 18 about travel itineraries from the server 10. Web page 30b informs 60 the user to wait while the browser downloads client executable 32, which is a travel browser for displaying the requested information 18 about travel itineraries. Web page 30b also informs the user of the time 62 it will take to download the client executable. Upon receiving the client executable 32, web browser 42 invokes JAVA™ interpreter 44 to execute the executable 32.

[0027] As shown in FIG. 4, client executable 32 presents a panel 70 on a web page 30c that informs 72 the user that the executable 32 is waiting for data 36 on travel itineraries associated with the user's request 12. When web browser 42 receives the data 36, client executable 32 processes the data, for example, by decoding, uncompressing, and preparing the data 36 for graphical presentation on the display 50.

[0028] As shown in FIG. 5, client executable 32 replaces the panel 70 (FIG. 4) on web page 30c with a new panel 74, which contains a graphical presentation 76 of such itinerary data as departure flights 76a and arrival flights 76b.

[0029] Referring to FIG. 6A, upon receiving (600) the request from browser 42, web server 28 transmits (602) a first segment of the web page 30c (FIGS. 4 and 5) to the browser 42. The first segment includes a directive to the browser 42 to request the client executable 32 from the server 32. The web server 28 invokes the travel module 34, causing the travel module to generate (604) another segment of the web page 30c containing a portion of the travel itinerary data 36. While the travel module is generating the segment of web page 30c, the web server 28 receives (612) a request for client executable 32 from browser 42, and transmits (614) client executable 32 to the browser 42. The web server 28 transmits at least part of client executable 32 while the travel module is generating the segment of the web page.

[0030] Web server 28 transmits (606) the generated segment of the web page to the browser 42 and checks (608) with the travel module 34 to determine whether there is another portion of the travel itinerary data 36 to be generated. If there is more data 36 to be generated, the web server 10 invokes the travel module 34 to generate (604) yet another segment of the web page. A part of the segment of the web page may be generated (604) while the previous segment of the web page is being transmitted.

[0031] Otherwise, if there is no more data to be generated, the server 10 terminates the process.

[0032] Referring to FIG. 6B, when the client computer 14a transmits (650) a data request query to the server 10, the client computer 14a uses web page 30b (FIG. 3) to inform (652) the user that the browser is waiting for the client executable 32 to be downloaded. When the browser 42 receives (654) the first segment of the web page 30c, the directive contained within the web page causes the web browser to transmit (656) a request for the client executable 32 from the server 10. Upon receiving (658) the client executable 32 from the server, java interpreter 44 executes the client executable 32 and informs (660) the user in panel 70 (FIG. 4) that the browser 42 is waiting for data from the server 10.

[0033] On receiving (662) another segment of the web page containing a portion of the travel itinerary data 36, client executable 32 decodes (664) the portion of the data and graphically displays (666) the decoded data in panel 74 (FIG. 5). Certain client executables 32 may also display an indication to the user that the new segment has been received. For example, they may update a display of the percentage of the travel itinerary data 36 that has been received. The client executable 32 then checks (668) whether the portion of the data 36 in the segment is the last portion, as will be described later with reference to FIG. 7C. If it is not the last portion of the data 36, the web page repeats the process (662–668) of receiving another segment of web page 30c. Otherwise, if it is the last segment, the web browser 42 terminates the process.

[0034] As shown in FIG. 7A, the first segment 80 of the web page 30c includes an HTML directive 82 to the browser 42 to request the client executable 32 from a URL 84 and invoke java interpreter 44 to execute the executable 32. Browser 42 responds to the first segment 80 by requesting the executable 32 and storing it in cache 52. The directive 82 also contains attributes that the java interpreter 44 should invoke the executable with. For instance, the code attribute 88 indicates to the interpreter 44 that the executable 32 should be invoked with no data, attributes 90 indicate the size of the panel 70 (FIG. 4) that the executable 32 should display, while attributes 92 indicate the spacing of data displayed in the panel 70. The first segment 80 also contains a set of parameters 94, including a list 96 of the locations where the executable 32 can find such information as logos and sounds.

[0035] As shown in FIG. 7B, the second segment 100 of the web page 30c also includes an HTML directive 102 to the browser to request the client executable 32 from the URL 84. However, the browser does not retrieve the executable 32 from the server 10 because the browser 42 finds the executable in cache 32. Although the directive 102 also contains attributes 104, 106 indicating the size and spacing that the applet should be invoked with, the values of the attributes are set to zero. Consequently, the second invocation of the executable 32 does not create a new panel. Directive 102 is associated with a parameter 108 that is also contained in the second segment 100 of the web page 30c. The parameter includes a first portion 110 of the travel data 36 for display by the executable 32. As previously described, server 10 may send any number of such segments 100 of the web page each containing a portion of the data. The server 10 may be configured to transmit segments of web pages containing differently sized portions 110 of the data 36, depending on the speed and reliability of the network 16. For most networks, the server 10 is configured to transmit portions of data that are larger than the portion 110.

[0036] As shown in FIG. 7C, the last segment 120 of the web page 30c is similar to the second segment 100 (FIG. 7B), but includes an additional parameter 122, which indicates to the executable 32 that there are no more data portions to be received. The client applet 32 checks (668) (FIG. 6B) each segment of the web page 30c for the parameter 122 to determine whether the portion of the data 36 contained in the segment is the last portion of the data. Additionally, the last segment 120 contains html keywords 124 that inform the browser 42 that the browser 42 has received the entire web page 30c.

[0037] The client executable 32 graphically displays the data 36 from the segments in the panel 74 (FIG. 5).

[0038] Referring to FIG. 8A, in an alternate embodiment of the invention, upon receiving (800) the request from browser 42, web server 28 generates (802) a session identity (ID) transmits (804) a web page to the browser 42 that includes the session ID along with a directive to the web browser 42 to request the client executable 32 from the server 10. The web server 28 invokes the travel module 34, causing the travel module to generate (806) the travel itinerary data 36. While the travel module 34 is generating the data 36, the web server 28 receives (814) a request for client executable 32 from browser 42, and transmits (816) client executable 32 to the browser 42. The web server 28 transmits at least part of client executable 32 while the travel module is generating the segment of the web page.

[0039] Web server 28 associates (808) the data 36 generated by travel module 34 with the session ID and checks (810) whether a request for data that includes the session ID has been received. If the request has not been received, the web server waits (810) for the request. Otherwise, if the request has been received, the web server transmits (812) the data to the requesting client computer 14a and terminates the process. The server 10 may also be configured to segment the generated data and transmit the segments in sequence.

[0040] Referring to FIG. 8B, in the alternate embodiment, when the client computer 14a transmits (850) a query to the server 10, the client computer 14a uses web page 30b (FIG. 3) to inform (852) the user that the browser is waiting for the client executable 32 to be downloaded. When the browser 42 receives (854) the web page with the session ID, the directive contained within the web page causes the web browser to transmit (856) a request for the client executable 32 from the server 10. Upon receiving (858) the client executable 32 from the server, java interpreter 44 executes the client executable 32 and informs (860) the user in panel 70 (FIG. 4) that the browser 42 is waiting for data from the server 10.

[0041] Client executable 32 transmits (862) a request for the travel data 36 along with the session ID to the server. On receiving (864) the data associated with the session ID from the server, client executable 32 decodes (866) the data and graphically displays (868) the decoded data in panel 74 (FIG. 5).

[0042] A number of embodiments of the invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. For example, the client executable may be stored on a different server from travel module 34 and the web page 30c configured so that it causes the web browser to download the client executable from the different server. The server 10 may include multiple processors to allow it to more effectively perform multiple tasks at the same time.

[0043] The invention may also be applied to other kinds of servers to perform functions that are not related to travel. For example, the invention may applied to a server that distributes music data along with an executable client for playing the music data.

[0044] Accordingly, other embodiments are within the scope of the following claims.