Browse Prior Art Database

Method for Providing Visual Delay Indicators Based on Historical Data Disclosure Number: IPCOM000016687D
Original Publication Date: 2003-Jul-09
Included in the Prior Art Database: 2003-Jul-09
Document File: 2 page(s) / 14K

Publishing Venue



Computer users are conditioned to expect quick response times from clicking buttons or hyperlinks in a web browser. When they don't receive these quick responses they are often disatisfied with the user interface, or worse, suspect that the interface is stalled or malfunctioning. This often causes the user to attempt a better response by resubmitting/refreshing the page. This can lead to instability in the backend application and cause the user to drive unintentional actions. Web applications are prone to this type of problem due to the nature of the request/response cycle.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 88% of the total text.

Page 1 of 2

Method for Providing Visual Delay Indicators Based on Historical Data

    This paper proposes a system for tracking the time required for generating a response for certain actions. This system would record the time an action takes to complete then updates a Metrics Repository with the data. The Repository keeps a running average of the action completion times. This average is used by the rendering code to decide whether an action needs a special depiction of the estimated time the action may take to complete.

Figure A depicts the process of rendering a hyperlink or action button on a web page. The server consults with the Metrics Repository to decided if the hyperlink needs a special iconic depiction of the expected time to completion of the task. Figure B depicts the process that a performed action will do to update the Metrics Repository with a running average of the time the action takes to complete.

Browser Requests Page

 Server Begins Building a Page Containing an Action Hyperlink

  Server Calls Renderer for Action Hyperlink

Renderer Consults Metrics Repository


Takes A Long Time?

Render Long Running


Renderer Hyperlink



Figure A - MR used to decide how to render a hyperlink


[This page contains 1 picture or other non-text object]

Page 2 of 2

   Action is Invoked From a Clicked Hyperlink Or Button

Timer is Created and Started

  Action Work Starts And Completion is Waited Upon

Timer Stops

 Total Time for Action Completion is Recorded and Averaged in the...