WO2012015598A1 - Highly reliable cross-session web application instrumentation - Google Patents
Highly reliable cross-session web application instrumentation Download PDFInfo
- Publication number
- WO2012015598A1 WO2012015598A1 PCT/US2011/043859 US2011043859W WO2012015598A1 WO 2012015598 A1 WO2012015598 A1 WO 2012015598A1 US 2011043859 W US2011043859 W US 2011043859W WO 2012015598 A1 WO2012015598 A1 WO 2012015598A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- instrumentation
- client
- server
- user
- computing devices
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
Definitions
- the present invention relates to managing the collection of user tracking data representing user interactions with web content at a client device. More specifically, the present invention relates to locally caching user tracking data at the client device and selectively transmitting the cached data.
- client devices may obtain news, television, weather information, and even a college education over a network from remotely- located computer services.
- client devices may take many forms, including but not limited to cell phones, personal digital assistants, laptops and desktop computers.
- a service provider may find it useful to know that users frequently hover their input focus (such as a mouse pointer) over a certain portion of the display, or that users rarely use certain controls provided by the services.
- Service providers may collect data reflecting user interactions with remotely- provided services for the additional purposes of user personalization of the services, user profiling, system usage metrics, and other research purposes.
- Remotely-provided services typically involve both client-side logic and server-side logic.
- the client-side logic of a service is typically responsible for generating a user interface through which a user may interact with the service.
- the server-side logic of a service is typically responsible for the content of the service, and for providing that content to the client.
- a user's clickstream conveys only part of the user's interaction with a web service.
- a clickstream may not indicate when and where users move their input focus while interacting with the service.
- a clickstream may not be able to indicate how a user made a particular selection.
- some web pages may provide a number of alternative input mechanisms (e.g. a clickable button, menu option, and a keyboard shortcut) to accomplish the same operation (e.g. saving a document in the application).
- the clickstream may indicate that the user selected the operation, but not which of the input mechanisms was used to initiate the operation.
- a clickstream may not indicate user interactions that are handled by client-side code, such as JAVASCRIPTTM or FLASH®, that is embedded in a web page delivered to clients by the service. It may be just as important to know how a user interacts with the interfaces generated by client-side code as it is to know a user's clickstream.
- client-side code such as JAVASCRIPTTM or FLASH®
- the communication bandwidth from the client-side logic to the server-side logic (the "upstream bandwidth”) is often significantly lower than the communication bandwidth from the server-side logic to the client-side logic (the “downstream bandwidth”). Consequently, sending to the server-side detailed information about what a user is doing on the client-side may consume an unacceptably large amount of the relatively small upstream bandwidth.
- the server would create the user interface elements and/or get a request for most, if not all, user actions via a post back (page reload).
- User tracking in these instances is accomplished by monitoring the user's clickstream generated by the user requests to the server as the user navigates the available resources.
- “Web 2.0" technologies have proliferated, these mechanisms to track user actions are no longer sufficient to capture the variety of ways users interact with "Web 2.0" interfaces.
- Current solutions attempt to either immediately send all instrumentation data at the time it is gathered, or to queue information about a user's interaction with a page and then flush the queue by sending the information to the server-side when the page unloads.
- FIG. 1 is a block diagram that depicts an example network arrangement 100 for collecting user tracking data from user interactions with a web application.
- FIG. 2 is a flowchart illustrating steps for collecting user tracking data, in accordance with an embodiment of the invention.
- FIG. 3 is a block diagram of a computer system on which embodiments of the invention may be implemented.
- 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 data (referred to herein as "instrumentation items") are cached in a client-side offline 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. Using these techniques, more information may be gathered and sent to the server-side without significantly interfering with the user experience.
- Using a client-side cache in this manner allows a service to gather more data about the user' s actions than would otherwise be feasible to instrument without interfering with the user experience or application performance. Being able to reliably save the instrumentation items on the client-side without having to immediately send them to the server-side data collection services allows a service to dynamically strike the right balance between the user experience, the amount of data gathered, and timeliness of reporting that data to the server-side.
- client-side caching allows "data throttling" for situations where it may be temporarily inconvenient or unfeasible to send (all) of the instrumentation items to the server-side.
- Situations in which instrumentation item transmission may be postponed include when a user is experiencing a degraded connection speed or where there in an unusually high load on the capturing service.
- client-side computer code is provided that can listen to or be given items of interest for instrumentation purposes.
- the code is implemented as a class (referred to herein as the "instrumentation class") in an object-oriented language.
- instrumentation class a class in an object-oriented language.
- use of an instrumentation class is merely one way in which client-side caching may be implemented, and the techniques described herein are not limited to an implementation that uses an instrumentation class.
- the techniques may be implemented using client-side routines that are spread over several different classes, or even by routines that are written in a
- the instrumentation class defines methods for storing the captured items in a client-side offline storage mechanism, such as HTML 5 Web Storage, an Adobe Flash application' s SharedObject, Microsoft Silverlight, or other client-side technology such as Google Gears.
- client-side offline storage mechanisms such as HTML 5 Web Storage, an Adobe Flash application' s SharedObject, Microsoft Silverlight, or other client-side technology such as Google Gears.
- client-side offline storage mechanisms such as HTML 5 Web Storage, an Adobe Flash application' s SharedObject, Microsoft Silverlight, or other client-side technology such as Google Gears.
- the instrumentation class code may be embedded directly in the web application content, or imported into the application content as a separately delivered library component.
- the client-side instrumentation code may be integrated into a web browser as an add-on or toolbar, or delivered as a standalone client-side application.
- the instrumentation items may be sent to the instrumentation class by event handlers in the application code that monitor user interactions with the application interface. For example, when a user selects a button, the code that implements the button may invoke a method of the instrumentation class, and pass to the method parameter values that indicate the user's interaction with the button.
- the parameters may convey a variety of information about the user's interaction, such as which button was selected, when the button was selected, and the specific operation that was initiated by the user' s selection of the button.
- the instrumentation class may itself listen for user actions and record those actions as instrumentation item data.
- the user interactions detected by the client application code may first be sent to a user event bus.
- the instrumentation class would listen to the user event bus to detect new instrumentation items that ready for input into the client-side offline storage mechanism.
- the event bus would provide a common point of entry for detected user interactions across the web application.
- other client-side code external to the remote application may monitor user interactions and deliver them to the instrumentation class through an appropriate interface.
- different values may be passed as parameters to the methods provided by the instrumentation class to affect how the instrumentation items are cached at the client-side, and when cached instrumentation items are sent to the server-side.
- the parameters whose values affect the operation of the client-side cache are referred to herein as "control parameters”.
- control parameters the parameters whose values affect the operation of the client-side cache.
- arameterized rules the rules by which the client-side cache operates are affected by the values passed to the control parameters.
- the processes that are instantiated based on the instrumentation class determine the optimal amount of data to cache in relation to (a) the current application state and (b) user activity before sending the instrumentation items to a capturing service over the network.
- the values passed to control parameters affect variables which in turn affect operation of the client-side cache.
- the variables that can be adjusted based on the values of the control parameters provided to the instrumentation class time elapsed, critical time periods, number of events, data size, user idle time, amount of network traffic, etc.
- time elapsed time elapsed
- critical time periods time elapsed
- number of events number of events
- data size data size
- user idle time amount of network traffic
- amount of network traffic etc.
- These variables are merely examples of the types of variables that can be used by the implementation class to affect how the client-side cache operates.
- the types and value of these variables may be established on an application-wide basis, or the developers of individual application components within the service may provide variables based on the specific requirements of each application component.
- control parameters may be used to assign varying degrees of priority to the variables that affect the operation of the client-side cache.
- instrumentation items stored in the offline storage mechanism may be ordered in a transmission queue based at least partially on the relative priorities of the variables.
- stored instrumentation items may be transmitted to the server-side in a different order than the order in which the user events occurred at the client.
- the client- side cache may send an older large instrumentation item to the server-side before sending a more recent small instrumentation item. Conversely, if "time elapsed" is assigned a low priority value, and "data size” is assigned a high priority value, then the client-side cache may send the newer small instrumentation item before the larger old instrumentation item.
- the variables that affect operation of the client- side cache may have one or more thresholds.
- a threshold may be established for "network connection speed". If the user' s detected network connection speed is above the threshold, the amount of time that instrumentation items are cached in the offline storage mechanism may be reduced. Conversely, if the user' s detected network connection speed is above the threshold, the amount of time that instrumentation items are cached in the offline storage mechanism may be increased.
- a second, lower threshold may be established for the network connection speed, where instrumentation items are not sent to the server-side at all if the user's detected speed falls below the second threshold.
- the thresholds associated with a variable may be dynamically tuned according to changing network, client-side, server-side, or other application conditions.
- the thresholds for a variable may be set initially when the user starts a new session, and may also be set or adjusted during a user's session in response to detecting a change in some condition.
- a rule may establish that specific
- instrumentation items should be treated as "critical”, where critical instrumentation items are sent to the server-side immediately, optionally bypassing the cache. Even if the session is terminated (page is unloaded) before all data has been sent successfully, the data is persisted on the client-side, and can be sent the next time the user visits the website or application.
- the negative impact the transmission of instrumentation items has on performance is further reduced by tokenizing the instrumentation items prior to sending the instrumentation items from the client-side to the server-side.
- instrumentation items can be "tokenized" by creating a mapping of large and/or repetitive portions of instrumentation items. These mappings may be session-specific, or the same mapping may be used across sessions.
- the instrumentation class sends out a single mapping item that the backend can utilize to expand the full portion of data for each received item.
- the entire URL of the page can be sent once, along with a mapping to a short token or ID (such as a number or MD5 hash).
- ID such as a number or MD5 hash
- instrumentation items are tokenized according to a known token mapping at the time they are selected from the offline storage mechanism and transmitted to the server-side.
- the mapping may include tokens that have been created for the current session or include token mappings generated in a previous session.
- the instrumentation class may continuously or periodically scan the offline storage mechanism in order to detect repetitive portions of the instrumentation item data in order to create new token mappings. Instrumentation items may then be tokenized in the offline storage mechanism prior to transmission, reducing the space needed to store the instrumentation item data.
- instrumentation items are stored in the client-side cache and have the ability to persist across user sessions. For example, a user session may end when the user logs out of a remote application or unloads the pages containing the remote application before all data currently in the cache has been transmitted.
- instrumentation items stored in the client-side cache may be coded according to a data schema that includes a session identification attribute in order to distinguish instrumentation item data across multiple sessions.
- Other example instrumentation item schema attributes may include a user ID, trace level, source, element, command, and timestamps.
- instrumentation items from a prior session may be detected in the cache when a user starts a new session and the items may be delivered as part of the new session's startup sequence.
- instrumentation items from prior sessions may be detected in the cache by comparing session IDs or timestamp attributes.
- instrumentation items detected from prior sessions may simply be added to the transmission queue for the current session and selected for transmission accordingly.
- the client-side code may store and retrieve instrumentation items from the offline storage mechanism using any available programmatic interface for such purposes depending on the particular cache implementation. Instrumentation items retrieved from the cache may be transmitted to the server-side using a number of communication protocols including, but not limited to, HTTP, HTML 5 sockets, or TCP/IP connection. The instrumentation item data may be transmitted to the receiving service as individual items or as a batched data object including multiple items. [0036] According to one embodiment, transmitted instrumentation items from the client-side cache may remain in the transmission queue until the client receives some confirmation of delivery from the server-side. For example, in one embodiment, transmitted instrumentation items may remain in the transmission queue until an HTTP 200 response, or any other similar delivery confirmation message depending on the protocol, is received from the server-side. According to another embodiment, a transmission retry mechanism may be implemented in order to attempt re-transmitting items for which no delivery confirmation message was received or were otherwise unsuccessfully transmitted to the server-side.
- FIG. 1 is a block diagram that depicts an example network arrangement 100 for collecting user tracking data from user interactions with a web application.
- a user at client device 110 opens up a web browser 112 and makes a request to server 120 for use of remote service 122.
- the server 120 sends back to the client device 110 web application data providing the user the ability to interact with remote service 122.
- the web application data will include code to be executed on the client device 110 for the purposes of tracking the user's interaction with the received web application.
- FIG. 2 is a flowchart that represents the lifecycle 200 of the web application on the client's device 110 after the client-side logic for the web application has been received by the client device 110.
- the client device 110 receives a web application from a web server, where the web application includes code for tracking user interactions.
- the web application may take many forms, including but not limited to code that is embedded in or that accompanies a web page that has been retrieved from the client.
- the web application is instantiated on the client's device 110 and supplies parameters for one or more program variables.
- the application checks the offline storage mechanism 114 for any user tracking data in the cache that may not have been transmitted to a server in a prior user session. Based on a determination at step 206 that user tracking data from a prior session exists in the storage, according to one embodiment in step 208, the application may either transmit the user tracking data to a server as part of the application' s start-up sequence, or add the user tracking data to a transmission queue instantiated for the current session for later transmission.
- the application begins tracking current user interactions with the web application at step 110.
- notifications of user actions with the web application are sent to the application for processing.
- the application stores data representing the user interactions in the offline storage mechanism 114 on the client device 110.
- the user interaction data remains in the offline storage mechanism 114 until, at step 214, the application detects some condition based upon one or more of the program variables triggering the application to send one or more of the user interaction data items to a server.
- the application may continue operating in this fashion until the user unloads the application on the client by closing the pages containing the application or otherwise halting execution of the code.
- the techniques described herein are implemented by one or more special-purpose computing devices.
- the special-purpose computing devices may be hard-wired to perform the techniques, or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more general purpose hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination.
- ASICs application-specific integrated circuits
- FPGAs field programmable gate arrays
- Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques.
- the special-purpose computing devices may be desktop computer systems, portable computer systems, handheld devices, networking devices or any other device that incorporates hard- wired and/or program logic to implement the techniques.
- FIG. 3 is a block diagram that illustrates a computer system 300 upon which an embodiment of the invention may be implemented.
- Computer system 300 includes a bus 302 or other communication mechanism for communicating information, and a hardware processor 304 coupled with bus 302 for processing information.
- Hardware processor 304 may be, for example, a general purpose microprocessor.
- Computer system 300 also includes a main memory 306, such as a random access memory (RAM) or other dynamic storage device, coupled to bus 302 for storing information and instructions to be executed by processor 304.
- Main memory 306 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 304.
- Such instructions when stored in storage media accessible to processor 304, render computer system 300 into a special- purpose machine that is customized to perform the operations specified in the
- Computer system 300 further includes a read only memory (ROM) 308 or other static storage device coupled to bus 302 for storing static information and instructions for processor 304.
- ROM read only memory
- a storage device 310 such as a magnetic disk or optical disk, is provided and coupled to bus 302 for storing information and instructions.
- Computer system 300 may be coupled via bus 302 to a display 312, such as a cathode ray tube (CRT), for displaying information to a computer user.
- a display 312 such as a cathode ray tube (CRT)
- cursor control 316 is Another type of user input device
- cursor control 316 such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 304 and for controlling cursor movement on display 312.
- This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.
- Computer system 300 may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 300 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 300 in response to processor 304 executing one or more sequences of one or more instructions contained in main memory 306. Such instructions may be read into main memory 306 from another storage medium, such as storage device 310. Execution of the sequences of instructions contained in main memory 306 causes processor 304 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
- Non- volatile media includes, for example, optical or magnetic disks, such as storage device 310.
- Volatile media includes dynamic memory, such as main memory 306.
- Common forms of storage media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge.
- Storage media is distinct from but may be used in conjunction with transmission media.
- Transmission media participates in transferring information between storage media.
- transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 302.
- transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infrared data communications.
- Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 304 for execution.
- the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer.
- the remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem.
- a modem local to computer system 300 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal.
- An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 302.
- Bus 302 carries the data to main memory 306, from which processor 304 retrieves and executes the instructions.
- the instructions received by main memory 306 may optionally be stored on storage device 310 either before or after execution by processor 304.
- Computer system 300 also includes a communication interface 318 coupled to bus 302.
- Communication interface 318 provides a two-way data communication coupling to a network link 320 that is connected to a local network 322. For example,
- communication interface 318 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line.
- ISDN integrated services digital network
- communication interface 318 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
- LAN local area network
- communication interface 318 sends and receives electrical
- Network link 320 typically provides data communication through one or more networks to other data devices.
- network link 320 may provide a connection through local network 322 to a host computer 324 or to data equipment operated by an Internet Service Provider (ISP) 326.
- ISP 326 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the "Internet" 328.
- Internet 328 uses electrical, electromagnetic or optical signals that carry digital data streams.
- the signals through the various networks and the signals on network link 320 and through communication interface 318, which carry the digital data to and from computer system 300, are example forms of transmission media.
- Computer system 300 can send messages and receive data, including program code, through the network(s), network link 320 and communication interface 318.
- a server 330 might transmit a requested code for an application program through Internet 328, ISP 326, local network 322 and communication interface 318.
- the received code may be executed by processor 304 as it is received, and/or stored in storage device 310, or other non- volatile storage for later execution.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP11812934.5A EP2599005A4 (en) | 2010-07-30 | 2011-07-13 | Highly reliable cross-session web application instrumentation |
CN2011800377267A CN103038759A (en) | 2010-07-30 | 2011-07-13 | Highly reliable cross-session web application instrumentation |
MX2013001159A MX2013001159A (en) | 2010-07-30 | 2011-07-13 | Highly reliable cross-session web application instrumentation. |
BR112013001841A BR112013001841A2 (en) | 2010-07-30 | 2011-07-13 | computer-implemented method for collecting user instrumentation data and one or more non-transient storage media |
CA2806179A CA2806179C (en) | 2010-07-30 | 2011-07-13 | Highly reliable cross-session web application instrumentation |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/848,042 | 2010-07-30 | ||
US12/848,042 US8892608B2 (en) | 2010-07-30 | 2010-07-30 | Highly reliable cross-session web application instrumentation |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012015598A1 true WO2012015598A1 (en) | 2012-02-02 |
Family
ID=45527805
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2011/043859 WO2012015598A1 (en) | 2010-07-30 | 2011-07-13 | Highly reliable cross-session web application instrumentation |
Country Status (7)
Country | Link |
---|---|
US (2) | US8892608B2 (en) |
EP (1) | EP2599005A4 (en) |
CN (1) | CN103038759A (en) |
BR (1) | BR112013001841A2 (en) |
CA (1) | CA2806179C (en) |
MX (1) | MX2013001159A (en) |
WO (1) | WO2012015598A1 (en) |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102011006898A1 (en) * | 2011-04-06 | 2012-10-11 | Bayerische Motoren Werke Aktiengesellschaft | Method for operating a computer unit, method for operating an application portal, computer unit, apparatus for operating an application portal and system |
CN102222086B (en) * | 2011-05-18 | 2014-11-26 | 广州市动景计算机科技有限公司 | Webpage viewing method and webpage viewing device based on mobile terminal as well as mobile terminal |
US20150163116A1 (en) * | 2011-07-29 | 2015-06-11 | Google Inc. | Client-side click tracking |
CN103544193B (en) * | 2012-07-17 | 2018-06-08 | 北京千橡网景科技发展有限公司 | Method and apparatus for recognizing network robot |
US9678978B2 (en) * | 2012-12-31 | 2017-06-13 | Carbonite, Inc. | Systems and methods for automatic synchronization of recently modified data |
US9178908B2 (en) * | 2013-03-15 | 2015-11-03 | Shape Security, Inc. | Protecting against the introduction of alien content |
CN103530232B (en) * | 2013-10-24 | 2016-04-06 | 北京经纬恒润科技有限公司 | A kind of software testing management framework establishment method and device |
US9270647B2 (en) | 2013-12-06 | 2016-02-23 | Shape Security, Inc. | Client/server security by an intermediary rendering modified in-memory objects |
US8954583B1 (en) | 2014-01-20 | 2015-02-10 | Shape Security, Inc. | Intercepting and supervising calls to transformed operations and objects |
US9003511B1 (en) | 2014-07-22 | 2015-04-07 | Shape Security, Inc. | Polymorphic security policy action |
US9438625B1 (en) | 2014-09-09 | 2016-09-06 | Shape Security, Inc. | Mitigating scripted attacks using dynamic polymorphism |
US9723085B1 (en) * | 2014-10-31 | 2017-08-01 | Google, Inc. | Transferring a state of user interaction with an online content item to a computer program |
US9712513B2 (en) * | 2015-10-05 | 2017-07-18 | Kony, Inc. | Identity management over multiple identity providers |
CN105224694A (en) * | 2015-11-10 | 2016-01-06 | 中国建设银行股份有限公司 | A kind of summary information querying method, Apparatus and system |
US11645659B2 (en) * | 2019-07-31 | 2023-05-09 | Nutanix, Inc. | Facilitating customers to define policies for their clouds |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040258053A1 (en) * | 2003-06-16 | 2004-12-23 | Mentat Inc. | Pre-fetch communication systems and methods |
US20070171921A1 (en) * | 2006-01-24 | 2007-07-26 | Citrix Systems, Inc. | Methods and systems for interacting, via a hypermedium page, with a virtual machine executing in a terminal services session |
US20070282951A1 (en) * | 2006-02-10 | 2007-12-06 | Selimis Nikolas A | Cross-domain solution (CDS) collaborate-access-browse (CAB) and assured file transfer (AFT) |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7523191B1 (en) * | 2000-06-02 | 2009-04-21 | Yahoo! Inc. | System and method for monitoring user interaction with web pages |
US20020087679A1 (en) * | 2001-01-04 | 2002-07-04 | Visual Insights | Systems and methods for monitoring website activity in real time |
US6901536B2 (en) * | 2001-05-24 | 2005-05-31 | Microsoft Corporation | Service quality monitoring system and method |
US20040103215A1 (en) * | 2002-11-26 | 2004-05-27 | Bmc Software, Inc. | Selective compression of web-based data transmissions |
US20050216844A1 (en) * | 2004-03-03 | 2005-09-29 | Error Brett M | Delayed transmission of website usage data |
US7707573B1 (en) * | 2003-12-31 | 2010-04-27 | Google Inc. | Systems and methods for providing and installing software |
US7526799B2 (en) * | 2004-06-30 | 2009-04-28 | International Business Machines Corporation | Method for tracking security attributes along invocation chain using secure propagation token |
CA2664824A1 (en) * | 2005-09-28 | 2007-04-05 | Feeva, Inc. | Systems and methods of network operation and information processing, including data acquisition, processing and provision and/or interoperability features |
US8504775B2 (en) * | 2007-03-12 | 2013-08-06 | Citrix Systems, Inc | Systems and methods of prefreshening cached objects based on user's current web page |
US8819080B2 (en) * | 2007-06-13 | 2014-08-26 | The Boeing Company | System and method for collection, retrieval, and distribution of data |
-
2010
- 2010-07-30 US US12/848,042 patent/US8892608B2/en active Active
-
2011
- 2011-07-13 MX MX2013001159A patent/MX2013001159A/en active IP Right Grant
- 2011-07-13 WO PCT/US2011/043859 patent/WO2012015598A1/en active Application Filing
- 2011-07-13 CN CN2011800377267A patent/CN103038759A/en active Pending
- 2011-07-13 CA CA2806179A patent/CA2806179C/en active Active
- 2011-07-13 BR BR112013001841A patent/BR112013001841A2/en not_active IP Right Cessation
- 2011-07-13 EP EP11812934.5A patent/EP2599005A4/en not_active Withdrawn
-
2014
- 2014-11-13 US US14/540,222 patent/US20150074153A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040258053A1 (en) * | 2003-06-16 | 2004-12-23 | Mentat Inc. | Pre-fetch communication systems and methods |
US20070171921A1 (en) * | 2006-01-24 | 2007-07-26 | Citrix Systems, Inc. | Methods and systems for interacting, via a hypermedium page, with a virtual machine executing in a terminal services session |
US20070282951A1 (en) * | 2006-02-10 | 2007-12-06 | Selimis Nikolas A | Cross-domain solution (CDS) collaborate-access-browse (CAB) and assured file transfer (AFT) |
Non-Patent Citations (1)
Title |
---|
See also references of EP2599005A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP2599005A1 (en) | 2013-06-05 |
MX2013001159A (en) | 2013-02-27 |
CA2806179C (en) | 2015-10-20 |
BR112013001841A2 (en) | 2016-05-31 |
EP2599005A4 (en) | 2017-06-07 |
CA2806179A1 (en) | 2012-02-02 |
CN103038759A (en) | 2013-04-10 |
US20150074153A1 (en) | 2015-03-12 |
US8892608B2 (en) | 2014-11-18 |
US20120030248A1 (en) | 2012-02-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2806179C (en) | Highly reliable cross-session web application instrumentation | |
US10572548B2 (en) | System and method for improving access to search results | |
US20190057200A1 (en) | System, apparatus, and method of collecting and processing data in electronic devices | |
US20200012770A1 (en) | System, apparatus, and method of collecting and processing data in electronic devices | |
US7877461B1 (en) | System and method for adding dynamic information to digitally signed mobile applications | |
US8510430B2 (en) | Intelligent performance monitoring based on resource threshold | |
US8549100B2 (en) | Technique for previously providing estimate of time required for processing | |
US8346889B1 (en) | Event-driven module loading | |
US8849981B2 (en) | Response time benchmarking | |
US20120209945A1 (en) | Optimizing Server Resources Using Multiple Retry For High Traffic Websites | |
US10754900B2 (en) | Access to network content | |
US8966059B2 (en) | Cached data detection | |
US8744990B2 (en) | Rule based, proactive web browsing | |
CN102799372B (en) | A kind of method for uploading of pictorial information and upload device | |
WO2004079544A2 (en) | Delayed transmission of website usage data | |
US20120060079A1 (en) | Discovering alternative user experiences for websites | |
KR102392095B1 (en) | Control triggering of function calls from content items | |
US20160379276A1 (en) | Electronic asset delivery and event tracking system | |
US9507655B2 (en) | Tracking asynchronous entry points for an application | |
US8935285B2 (en) | Searchable and size-constrained local log repositories for tracking visitors' access to web content | |
US8856140B2 (en) | Querying dialog prompts using hash values | |
US8549071B2 (en) | Methods and systems for transferring client device data over a network | |
US8898263B2 (en) | Detecting change of settings stored on a remote server by making use of a network filter driver | |
KR20190090862A (en) | Redirection | |
US9959300B1 (en) | Systems and methods for article location and retrieval |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201180037726.7 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11812934 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2806179 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2013/001159 Country of ref document: MX |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011812934 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112013001841 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112013001841 Country of ref document: BR Kind code of ref document: A2 Effective date: 20130124 |