Long running requests
First Claim
1. A computer-implemented method for processing long-running requests, comprising:
- sending a first page request to render an HTML page;
wherein the HTML page includes at least one control;
receiving HTML from the first page result;
rendering the HTML;
generating a second page request;
wherein the second page request is a long-running request that requests the control to be rendered;
receiving data a rate that avoids a timeout; and
displaying a progress UI within the control until the long-running request is completed while maintaining the state of the HTML page.
2 Assignments
0 Petitions
Accused Products
Abstract
A progress UI is displayed within a user'"'"'s web page for long-running requests. For each long-running request, a progress UI is displayed to the user indicating that the long-running request is being processed until the long-running request has been processed. The progress UI may be a progress indicator showing the user the status of the processing, or the status message could be some other message to the user indicating that the long-running request is still being processed. While the long-running request is being processed, data is sent from the server to the user'"'"'s browser at a rate such that the server performing the long-running request does not time out. The current state of a web page may be maintained such that when a long running request is made the web page that contains the control that issued the long-running request is not automatically refreshed when the long running request takes place.
-
Citations
20 Claims
-
1. A computer-implemented method for processing long-running requests, comprising:
-
sending a first page request to render an HTML page;
wherein the HTML page includes at least one control;
receiving HTML from the first page result;
rendering the HTML;
generating a second page request;
wherein the second page request is a long-running request that requests the control to be rendered;
receiving data a rate that avoids a timeout; and
displaying a progress UI within the control until the long-running request is completed while maintaining the state of the HTML page. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A computer-readable medium having computer-executable instructions for processing long-running requests, the instructions comprising:
-
sending a first page request to a server;
wherein a first page includes at least one control;
rendering the first page in response to a result received in response to the first request;
sending a second page request;
wherein the second page request is a long-running request that requests the control to be rendered; and
displaying a progress UI within the control until the long-running request is completed;
wherein the progress UI is displayed using HTML and wherein the first page is maintained while the long-running request is being processed. - View Dependent Claims (10, 11, 12, 13, 14, 15)
-
-
16. A system for processing long-running requests, comprising:
-
a server comprising;
a processor and a computer-readable medium;
an operating environment stored on the computer-readable medium and executing on the processor; and
a program operating under the control of the operating environment and operative to perform actions, including;
receiving a first page request from a client that includes a control within an HTML page associated with the first page request;
sending HTML in response to the first page request;
receiving a second page request from the control;
wherein the second page request is a long-running request;
performing operations relating to the long-running request;
streaming data to the client at a rate that avoids a timeout from being detected; and
providing a result of the calculation to the client;
the client that is coupled to the server, comprising;
a processor and a computer-readable medium;
an operating environment stored on the computer-readable medium and executing on the processor;
a display; and
a browser operating under the control of the operating environment and operative to perform actions, including;
sending the first page request to the server;
rendering a first page in response to the received HTML;
sending the second page request; and
displaying a progress UI within the control until the long-running request is completed while maintaining a state of the first page;
wherein the progress UI is displayed using HTML. - View Dependent Claims (17, 18, 19, 20)
-
Specification