Data conduit

• US 20060184613A1
• Filed: 03/31/2005
• Published: 08/17/2006
• Est. Priority Date: 02/15/2005
• Status: Abandoned Application

• Current Assignee: XRS Corporation (Solera Holdings Incorporated)
• Original Assignee: XRS Corporation (Solera Holdings Incorporated)
• Inventors: Thayer, Peter A., Ferguson, Jeffrey, Exley, Patrick T., Ratcliff, Margaret L., Smisek, Eric J., Stienessen, David J.
• Application Number:
  US11/094,854
• Publication Number:
  US 20060184613A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

This disclosure describes techniques for data transfer between web browsers and a server computer in a web-based environment. In particular, this disclosure describes a data transfer system that includes a set of web-based applications designed to rapidly transfer large amounts of data as a background task, and similarly transfer updated data without requiring a user to request the updated data. In accordance with the invention, a cache of data is stored on the web browser. The web browser and server computer make use of web browser components or add-ins, referred to herein as data conduit modules. The data conduit modules provide the web browsers with the ability to poll the server for updates, as a background task. Additionally, the data conduit modules are capable of retrieving changed data from the server and updating the data in the local cache. Such updates can occur automatically, and independent of user requests.

Claims

1. A method comprising:

receiving a subset of data at a web browser from a server computer in response to a request from the web browser for the subset of data, the request for the subset of data being a user-initiated event initiated by a user at the web browser;

caching the subset of data at the web browser;

automatically sending a request from the web browser for updated data, the request for the updated data being a web application-initiated event initiated automatically by the web browser;

receiving the updated data at the web browser from the server; and

updating the cached subset of data at the web browser to reflect the updated data.

2. The method of claim 1, wherein receiving the updated data occurs over a default browser port.

3. The method of claim 1, wherein the request for updated data comprises a request for data that has changed since a most recent request, and wherein the request for updated data includes an indication of a time of the most recent request.

4. The method of claim 1, wherein the user makes the request for the subset of data via a user interface application of the web browser.

5. The method of claim 4, further comprising raising an event to the user interface that the subset of data has been received.

6. The method of claim 1, further comprising repeatedly sending an automatic request for updated data from the web browser on an interval, wherein the interval of the automatic request is configurable.

7. The method of claim 1, wherein the subset of data comprises fleet management data, wherein the user is a dispatcher, and wherein the web browser is used by the dispatcher in viewing the fleet management data.

8. The method of claim 1, wherein updating the cached subset of data at the web browser comprises prioritizing an order of updating the cached subset of data such that a currently active set of the subset of data on the web browser is updated prior to updating a currently inactive set of the subset of data.

9. The method of claim 1, wherein the user does not initiate the request for updated data.

10. The method of claim 1, further comprising viewing the subset of data at the web browser.

11. The method of claim 1, wherein the updated data comprises one of an addition, edit, or deletion to the subset of data.

12. A computer-readable medium comprising instructions that when executed by a web browser of a fleet management system cause the web browser to:

receive fleet management data from a server computer in response to a request from the web browser for the fleet management, the request for the fleet management being a user-initiated event initiated by a user at the web browser;

cache the fleet management data at the web browser;

automatically send a request from the web browser for updated data, the request for the updated data being a web application-initiated event initiated automatically by the web browser;

receive the updated data at the web browser from the server; and

update the cached fleet management data at the web browser to reflect the updated data.

13. A method comprising:

storing a set of data in a database;

receiving a request from a first web browser for a first subset of the set of data, the request for the first subset of the set of data being a user-initiated event initiated by a first user at the first web browser;

sending the first subset of the set of data to the first web browser;

receiving a data update from a second web browser, the data update being entered by a second user at the second web browser with respect to a second subset of the set of data;

updating the set of data in the database based on the data update received from the second web browser;

receiving a request for updated data from the first web browser, the request for the updated data being a web application-initiated event initiated automatically by the first web browser; and

sending the updated data to the first web browser in response to the request for the updated data.

14. The method of claim 13, further comprising marking the updated data in the database with a time stamp.

15. The method of claim 14, further comprising:

checking the database for data having a time stamp more recent than a most recent request of the first web browser, a time of the most recent request being indicated in the request for updated data,

wherein sending the updated data comprises sending data having a time stamp more recent than the time of the most recent request.

16. The method of claim 13, further comprising compressing the first subset of the set of data prior to sending the first subset of the set of data.

17. The method of claim 13, further comprising sending the first subset of the set of data and the updated data as attachments to Extensible Markup Language (XML)-based Simplified Object Access Protocol (SOAP) messages.

18. The method of claim 13, wherein the set of data comprises fleet management data, wherein the first and second users are dispatchers, and wherein the web browsers are used by the dispatchers in viewing subsets of the fleet management data.

19. The method of claim 13, wherein the data update comprises one of an addition, edit, or deletion to the second subset of the set of data.

20. A computer-readable medium comprising instructions that when executed by a server computer of a fleet management system cause the server computer to:

store a set of fleet management data in a database;

receive a request from a first web browser for a first subset of the set of fleet management data, the request for the first subset of the set of fleet management data being a user-initiated event initiated by a dispatcher at the first web browser;

send the first subset of the set of fleet management data to the first web browser;

receive a data update from a second web browser, the second web browser being associated with a vehicle of a fleet managed by the fleet management system;

update the set of fleet management data in the database based on the data update received from the second web browser;

receive a request for updated data from the first web browser, the request for the updated data being a web application-initiated event initiated automatically by the first web browser; and

send the updated data to the first web browser in response to the request for the updated data.

21. A device comprising:

a local cache that stores a subset of data;

a user interface application that displays at least some of the subset of data from the local cache;

a data conduit client module that;

receives the subset of data from a server computer in response to a request from the data conduit client module for the subset of data, the request for the subset of data being a user-initiated event initiated by a user at the device;

stores the subset of data to the local cache;

automatically sends a request for updated data, the request for the updated data being a web application-initiated event initiated automatically by the data conduit client module;

receives the updated data from the server; and

updates the stored subset of data in the local cache to reflect the updated data.

22. The device of claim 21, wherein the data conduit client module repeatedly sends an automatic request for updated data on an interval, wherein the interval of the automatic request is configurable.

23. The device of claim 21, wherein the subset of data stored in the local cache comprises fleet management data, wherein the user is a dispatcher, and wherein the web browsers are used by the dispatchers in viewing at least some of the fleet management data.

24. The device of claim 21, wherein the received updated data includes one of an addition, edit, or deletion to the subset of data.

25. A device comprising:

a central database that stores a set of data; and

a data conduit server module that;

receives a request from a first web browser for a first subset of the set of data, the request for the first subset of the set of data being a user-initiated event initiated by a first user at the first web browser;

sends the first subset of the set of data to the first web browser;

receives a data update to a second subset of the set of data from a second web browser, the data update being entered by a second user at the second web browser;

updates the set of data in the central database based on the data update received from the second web browser;

receives a request for updated data from the first web browser, the request for the updated data being a web application-initiated event initiated automatically by the first web browser; and

sends the updated data to the first web browser in response to the second request.

26. The device of claim 25, wherein the data conduit server module further marks the updated data with a time stamp.

27. The device of claim 25, wherein the set of data comprises fleet management data, wherein the first and second users are dispatchers, and wherein the web browsers are used by the dispatchers in viewing at least some of the fleet management data.

28. The device of claim 25, wherein the data update comprises one of an addition, edit, or deletion of another subset of the set of data.

29. A system comprising:

a server that stores and updates a set of data;

a plurality of web browsers that each;

send data updates to the server to update the set of data;

automatically send requests to the server for updates to a subset of the set of data, wherein the automatic requests for updates are web application-initiated events sent by the web browsers;

receive data updates from the server in response to the web application-initiated events; and

store the data updates to a local cache that contains the subset of the set of data.

30. The system of claim 29, wherein the data updates are one of additions, edits, or deletions to the subset of the set of data in the local cache.