HIGHLY RELIABLE CROSS-SESSION WEB APPLICATION INSTRUMENTATION

• US 20120030248A1
• Filed: 07/30/2010
• Published: 02/02/2012
• Est. Priority Date: 07/30/2010
• Status: Active Grant

• Current Assignee: University of Phoenix Incorporated
• Original Assignee: Apollo Education Group, Inc.
• Inventors: Blinnikka, Tomi J.
• Granted Patent: US 8,892,608 B2
• Time in Patent Office: Days
• US Class Current: 707/803
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

A reliable caching mechanism is provided for client-side caching of data that captures user interaction with a remote service, where users interact with the remote service through a computing device. Such instrumentation items are cached in a client-side offline queue. Within the client-side queue, the gathered instrumentation items survive between user sessions with the remote service. Because the client-side does not lose the instrumentation items that were gathered in a session when the session ends, those instrumentation items do not all need to be transferred to the server-side at or prior to the termination of the session in which the instrumentation items are collected. Instead, the instrumentation items may be sent to the server-side at times that will have less impact on the user experience, such as when the computing device is otherwise idle.

Claims

1. A computer-implemented method for collecting user instrumentation data, the method comprising the steps of:

during a first session between a remote service and a client, detecting an interaction by a user with an interface that is displayed on the client, wherein the interface is an interface of a web application associated with the remote service;

wherein the remote service is hosted at a server that is remote relative to the client;

in response to detecting said user interaction, storing an instrumentation item representing said user interaction in a client-side offline storage mechanism;

retaining the instrumentation item in the client-side offline storage mechanism after the first session has terminated; and

during a second session between the remote service and the client, transmitting said instrumentation item from said client-side offline storage mechanism to a server-side data collection service;

wherein the method is performed by one or more computing devices.

2. The method of claim 1 wherein the step of storing the instrumentation item is performed by client-side logic that is sent to the client from the server that hosts the remote service.

3. The method of claim 1, further comprising, before performing the step of transmitting:

receiving parameter values provided by said web application for one or more application variables; and

determining when to transmit said instrumentation item to said server-side collection service based, at least in part, on the one or more application variables.

4. The method of claim 1, wherein storing the instrumentation item includes placing said instrumentation item in a queue for transmission to said server-side collection service.

5. The method of claim 4, further comprising:

ordering said instrumentation item in the transmission queue relative to other instrumentation items in the transmission queue based at least partially upon one or more variables, wherein values for said one or more variables are provided by the web application;

transmitting said instrumentation items to said server-side collection service based on the order in which the transmission items are stored in the transmission queue.

6. The method of claim 5, wherein the variables include a variable that represents at least one of:

user idle time, time elapsed in the offline storage mechanism, network connection speed, number of instrumentation items in the offline storage mechanism, or data size of storage mechanism.

7. The method of claim 5, further comprising:

associating one or more specified thresholds with said one or more variables; and

using said one or more specified thresholds to determine when to transmit said instrumentation item to said server-side collection service.

8. The method of claim 7, further comprising:

detecting that some application or network condition has changed; and

in response to detecting that some application or network condition has changed, adjusting one or more of said specified thresholds.

9. The method of claim 1, further comprising:

creating a token mapping for one or more portions of one or more instrumentation items stored in said client-side offline storage mechanism;

transmitting an item representing said created token mapping to said server-side collection service; and

tokenizing one or more other instrumentation items in said client-side offline storage mechanism based on the token mapping.

10. The method of claim 1, the step of transmitting further comprising:

detecting a delivery confirmation message from said server-side collection service indicating receipt of said instrumentation item; and

based upon detecting said delivery confirmation message, removing said instrumentation item from said client-side offline storage mechanism.

11. The method of claim 1, further comprising:

detecting that a delivery confirmation message from said server-side collection service indicating receipt of said transmitted instrumentation item has not been received after a specified period of time;

based upon detecting that said delivery confirmation message has not been received after a specified period of time, retransmitting said instrumentation item to said server-side collection service.

12. The method of claim 1, wherein said client-side offline storage mechanism is a persistent component of a web browser.

13. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 1.

14. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 2.

15. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 3.

16. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 4.

17. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 5.

18. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 6.

19. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 7.

20. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 8.

21. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 9.

22. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 10.

23. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 11.

24. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of the method recited in claim 12.