US20080052351A1 - System and method for preventing timeout of a client - Google Patents
System and method for preventing timeout of a client Download PDFInfo
- Publication number
- US20080052351A1 US20080052351A1 US11/931,264 US93126407A US2008052351A1 US 20080052351 A1 US20080052351 A1 US 20080052351A1 US 93126407 A US93126407 A US 93126407A US 2008052351 A1 US2008052351 A1 US 2008052351A1
- Authority
- US
- United States
- Prior art keywords
- state
- refresh
- client
- task
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/28—Timers or timing mechanisms used in protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Definitions
- This invention relates to preventing timeout. More particularly, it relates to preventing timeout of a browser in a client/server system.
- Java Servlets are used in conjunction with web browsers.
- the web browser acts as the client.
- the servlet resides on the server side.
- user-entered data on the page such as information to make an on-line purchase of goods, may be sent to the servlet for processing.
- the servlet then receives that data and takes appropriate actions, such as verifying the credit card number and checking inventory to make sure the purchase can be fulfilled.
- the web browser may time-out and show an error message to the effect that the page being requested can not be obtained or that communication was lost with the web server.
- the servlet will eventually finish processing the user's data, but because of the timeout, the web page that the servlet returns to the browser after the data has been processed will go undisplayed.
- FIG. 1 represents a server/client system in accordance with the preferred embodiment of the invention.
- FIG. 2 is a diagrammatic representation of the threads of FIG. 1 .
- FIGS. 3A-3C are a flow chart of an exemplary embodiment of the method of the invention.
- FIG. 4 is class diagram illustrating thread I of FIG. 2 .
- a system and method for monitoring task progress in a Java servlet is used to avoid premature timeout of a browser.
- a bar graph representation of percentage of the task completion is returned from the servlet in a hypertext language markup, such as a JavaScript/HTML markup, on short time intervals (i.e., every 5 seconds).
- This bar graph can also be accompanied by text displaying any pertinent progress information.
- the instruction to request an updated representation of the progress is received by the browser in a meta tag from the servlet. This time interval is set to be less than the browser time-out value, so the browser will never time-out.
- the progress representation allows the user to see and understand how much progress has been made in completing the task, the browser does not timeout, and the user can estimate when the task will be completed.
- server 20 and client 30 are coupled through a network 22 .
- Server 20 has a servlet 24 running in thread I and an application task 26 running in thread II.
- Client 30 has a browser, in which progress bar 34 may be displayed responsive to servlet 24 indicating the state of completion of application task 26 in thread II.
- a meta tag is sent by servlet 24 in a first thread to keep a browser 32 from timing out during execution of application task 26 in a second thread.
- a meta tag is a piece of html markup that describes a document, and can define an interval that sets a refresh interval: after that interval, a client returns to the server to get a new copy of the page being displayed at client.
- This meta tag is an existing part of html, and is used by the preferred embodiment of the present invention to refresh an html page with information from a Java servlet.
- HTML and JavaScript at client browser displays progress bar/text at browser. Each time interval t the client goes to the server servlet 24 for an update for the progress bar 34 . That progress bar is tracking the progress of an application on a separate thread II.
- Servlet 24 responds by building a new HTML page with JavaScript to send back to client 30 a new display for browser display 32 with progress bar 34 updated to reflect current progress of application 26 .
- application 26 on thread II completes or goes to error state, the response from servlet 24 does not include the meta tag—so the page is done and no further refreshing is done in response to a meta tag.
- application 28 runs in thread II 26 , and as is represented by line 35 periodically posts its status (completion or error state) to task status 23 , which runs in thread I 24 .
- Thread I also includes user interface 25 .
- user interface accesses task status 23 to ascertain the current status of application 28 .
- user interface initializes user 31 to an initial state which includes a meta tag having a refresh attribute t.
- user 31 responsive to that refresh attribute t, periodically posts a refresh request to user interface 25 , which responds with a new state including an updated representation of the status of application 28 .
- Refresh attribute t is set at a time interval less than the timeout period for user 31 so that, as long as user 31 receives and responds to a state refresh including the meta tag, user 31 will not timeout.
- a Java user interface class presents a series of HTML screens (a wizard) to the user, each for collecting data from him for setting up an application task 28 in thread II.
- the data on the page is submitted to the Java Servlet 24 and is stored in this Java class.
- this servlet class 24 is represented by B2BCatalogPublishWizardForm.
- a subclass of ProgressBarTask is created (in this example, PublishTask). All data needed to perform the publish task is passed on to this newly created object.
- step 46 the new ProgressBarTask creates a TaskStatus object, which holds the percentage complete of the task to run, and some message text set by the object user.
- the ProgressBarTask also owns a ProgressBar object.
- step 48 application task 28 is run in a separate thread II from servlet 24 , which runs in thread I.
- the ProgressBarTask subclass object is sent to the classes handling the long operation (publish) in that separate thread. Those classes are in charge of using the PublishTask object to set the TaskStatus that it owns with new percentages and messages when it reaches specific milestones.
- step 50 updates to task status are periodically posted to the progress bar object by progress bar task. This is the data that will be read every t seconds when an update is required.
- servlet 24 sends to browser 32 an HTML page with progress indicator 34 (initially set to 0% completion) and a meta tag with a refresh attribute of t.
- step 54 browser 32 displays progress bar 34 .
- step 56 periodically, such as when an update is required to the HTML page with progress indicator 34 , the ProgressBar task takes the data from the TaskStatus object, and gives it to the ProgressBar object.
- the ProgressBar object uses that data to create a new HTML page to be returned in step 60 by the Java Servlet 24 to browser 32 .
- this HTML page contains a meta tag with a refresh attribute set to a default of t seconds. This will cause in step 54 a post to the Java Servlet 24 in t seconds, causing in step 56 the user interface class (i.e. B2BCatalogPublishWizardForm) to ask the ProgressBarTask subclass to get a new HTML page from ProgressBar.
- the user interface class i.e. B2BCatalogPublishWizardForm
- step 60 The meta tag with the refresh attribute is returned in step 60 in the HTML markup until in step 58 an error in or completion of task 26 is detected and, at that time, in step 62 the interface returns the HTML markup without the meta tag. This prevents an infinite refresh of the progress HTML page.
- step 64 a button is presented on the HTML page that takes the user to another page so that he can continue with his use of the browser.
- a ProgressBarTask subclass is shared between two threads I and II.
- Thread I consumes the TaskStatus data from it, and user interface thread II updates it.
- Thread I is the user interface class which can make calls to get a new HTML page to show the user the current task status, and the thread II is the class or classes performing the actual task 26 .
- the object model of FIG. 4 and Tables I-IV illustrate how a progress indicator meta tag having a refresh attribute is used to prevent browser time-out during application execution when publishing large electronic catalog in Connect for the IBM iSeries. All objects of FIG. 4 reside within Java servlet 24 (iSeries Connect is one Java Servlet). The Java code of Tables I-IV illustrate an exemplary embodiment of the invention for iSeries Connect.
- a class diagram illustrates progress bar task 10 (Table I), task status 12 (Table II), progress bar 14 (Table III), publish task 16 (Table IV), and application wizard 18 .
- progress bar task class 10 has a progress bar class 14 .
- progress bar task class 10 has a task status class 12 .
- publish task 16 extends progress bar task class 10 .
- application wizard class 18 has a publish task class 16 .
- Progress bar task class 10 returns html to browser 32 which contains progress bar 34 information.
- Table I sets forth a Java code statement of an exemplary progress bar task class 10 .
- Task status class 12 contains information on how complete is thread II 26 , or its error state.
- Progress bar class 14 is a data holder for the refresh rate on the meta tag of browser 32 , and is also used as an interface to update application task 28 thread II 26 progress.
- Publish task class 16 is an extended class of progress bar task class 10 with specific information for application task 28 thread II 26 (what is it and what kind of data does it need.)
- a publish task is a subclass of progress bar task. It is needed because a publish is a long operation that needs to be monitored by a progress bar. The kind of data it needs, for example, is the catalog format that will be published, who the catalog supplier is, if it is a local or remote catalog, etc.
- Table IV contains a Java code representation of an exemplary publish task class 16 .
- Application wizard class 18 is a method for starting application task 28 thread II 26 . Upon completing, application wizard class 18 induces progress bar 34 . Class 18 is a wizard that interacts with the user to obtain information on how to publish, for example, an electronic catalog. At the end of the wizard, when a finish button is clicked, publish task class 16 is instantiated.
- An example of such a wizard is the B2BCatalogPublishWizardForm at
- Thread II 26 once spawned, sets/resets its progress bar by executing the Java code
- Application task 28 on thread II updates task status class 12 , and progress bar task class 10 builds an HTML response to client 30 showing in the statement
- progress bar task class 10 returns HTML without the refresh meta tag and a progress bar which shows a completion or stopped state.
- each step of the method may be executed on any general computer, such as IBM Systems designated as zSeries, iSeries, xSeries, and pSeries, or the like and pursuant to one or more, or a part of one or more, program elements, modules or objects generated from any programming language, such as C++, Java, P1/1, Fortran or the like.
- each said step, or a file or object or the like implementing each said step may be executed by special purpose hardware or a circuit module designed for that purpose.
Abstract
A system for preventing timeout of a client interface accessing a main Java Servlet executing in a first thread which monitors an application executing in a second thread. A task status object is accessed by the application to post its completion state and by the client interface responsive to a state refresh request to post a state refresh response including the completion state to the client. The state refresh response selectively includes a refresh attribute instructing the client to periodically post the state refresh request. Upon the application going to completion or error state, subsequent state refresh responses do not include the refresh attribute.
Description
- This is a continuation of U.S. patent application Ser. No. 10/126,484, filed Apr. 19, 2002, entitled “System and Method for Preventing Timeout of a Client”, which is herein incorporated by reference. This application claims priority under 35 U.S.C. §120 of U.S. patent application Ser. No. 10/126,484, filed Apr. 19, 2002.
- 1. Technical Field of the Invention
- This invention relates to preventing timeout. More particularly, it relates to preventing timeout of a browser in a client/server system.
- 2. Background Art
- Java Servlets are used in conjunction with web browsers. The web browser acts as the client. The servlet resides on the server side. When an event occurs on a web page, such as clicking on a “submit” button, user-entered data on the page, such as information to make an on-line purchase of goods, may be sent to the servlet for processing. The servlet then receives that data and takes appropriate actions, such as verifying the credit card number and checking inventory to make sure the purchase can be fulfilled.
- If the servlet takes a lengthy period of time to process that data, the web browser may time-out and show an error message to the effect that the page being requested can not be obtained or that communication was lost with the web server. The servlet will eventually finish processing the user's data, but because of the timeout, the web page that the servlet returns to the browser after the data has been processed will go undisplayed.
- Even if the data is able to be processed within the time-out period enforced by the browser, the processing may still be lengthy. Without a monitoring system that uses words and/or a pictorial to indicate the progress of the data processing to the user, the user would only see an hourglass while the mouse is hovering over the browser. This has been a source of frustration for users encountering this phenomenon.
- It is an object of the invention to provide a system and method for avoiding premature timeout of a browser while awaiting completion of an application.
- A system and method for preventing timeout by initializing an application for execution; initializing a client state with a refresh attribute, the refresh attribute specifying a time interval for posting state refresh requests; responsive to the state refresh request from the client, returning to the client a refreshed application state selectively including a refresh attribute while the application is executing and not including the refresh attribute upon said application completing execution or going into an error state.
- Other features and advantages of this invention will become apparent from the following detailed description of the presently preferred embodiment of the invention, taken in conjunction with the accompanying drawings.
-
FIG. 1 represents a server/client system in accordance with the preferred embodiment of the invention. -
FIG. 2 is a diagrammatic representation of the threads ofFIG. 1 . -
FIGS. 3A-3C are a flow chart of an exemplary embodiment of the method of the invention. -
FIG. 4 is class diagram illustrating thread I ofFIG. 2 . - In accordance with the preferred embodiment of the invention, a system and method for monitoring task progress in a Java servlet is used to avoid premature timeout of a browser. In an exemplary embodiment, on periodic request from the browser, a bar graph representation of percentage of the task completion is returned from the servlet in a hypertext language markup, such as a JavaScript/HTML markup, on short time intervals (i.e., every 5 seconds). This bar graph can also be accompanied by text displaying any pertinent progress information. The instruction to request an updated representation of the progress is received by the browser in a meta tag from the servlet. This time interval is set to be less than the browser time-out value, so the browser will never time-out. The progress representation allows the user to see and understand how much progress has been made in completing the task, the browser does not timeout, and the user can estimate when the task will be completed.
- Referring to
FIG. 1 ,server 20 andclient 30 are coupled through anetwork 22.Server 20 has aservlet 24 running in thread I and anapplication task 26 running in thread II.Client 30 has a browser, in whichprogress bar 34 may be displayed responsive to servlet 24 indicating the state of completion ofapplication task 26 in thread II. - In accordance with the preferred embodiment of the invention, a meta tag is sent by servlet 24 in a first thread to keep a
browser 32 from timing out during execution ofapplication task 26 in a second thread. - A meta tag is a piece of html markup that describes a document, and can define an interval that sets a refresh interval: after that interval, a client returns to the server to get a new copy of the page being displayed at client. This meta tag is an existing part of html, and is used by the preferred embodiment of the present invention to refresh an html page with information from a Java servlet.
- HTML and JavaScript at client browser displays progress bar/text at browser. Each time interval t the client goes to the server servlet 24 for an update for the
progress bar 34. That progress bar is tracking the progress of an application on a separate thread II. - Servlet 24 responds by building a new HTML page with JavaScript to send back to client 30 a new display for
browser display 32 withprogress bar 34 updated to reflect current progress ofapplication 26. Whenapplication 26 on thread II completes or goes to error state, the response fromservlet 24 does not include the meta tag—so the page is done and no further refreshing is done in response to a meta tag. - Referring to
FIG. 2 , application 28 runs in thread II 26, and as is represented byline 35 periodically posts its status (completion or error state) to task status 23, which runs in thread I 24. Thread I also includes user interface 25. As is represented byline 36, user interface accesses task status 23 to ascertain the current status of application 28. As is represented byline 37, user interface initializes user 31 to an initial state which includes a meta tag having a refresh attribute t. As is further represented byline 37, user 31, responsive to that refresh attribute t, periodically posts a refresh request to user interface 25, which responds with a new state including an updated representation of the status of application 28. Until application 28 posts completion or error to task status 23, user interface 25 will respond to refresh requests from user 31 with a state refresh that includes the refresh attribute. Upon task status 23 being posted by application 28 to error or complete state, the response from user interface 25 to user 31 will not include the refresh attribute t and user 31 ceases posting periodic refresh requests to user interface 25. Refresh attribute t is set at a time interval less than the timeout period for user 31 so that, as long as user 31 receives and responds to a state refresh including the meta tag, user 31 will not timeout. - Referring to
FIGS. 3A-3C in connection withFIG. 1 , an exemplary embodiment of the invention is presented. Instep 40, a Java user interface class presents a series of HTML screens (a wizard) to the user, each for collecting data from him for setting up an application task 28 in thread II. Between each screen, in step 42, the data on the page is submitted to the Java Servlet 24 and is stored in this Java class. In an exemplary embodiment, thisservlet class 24 is represented by B2BCatalogPublishWizardForm. Once all data has been collected from the user, instep 44, a subclass of ProgressBarTask is created (in this example, PublishTask). All data needed to perform the publish task is passed on to this newly created object. - In
step 46, the new ProgressBarTask creates a TaskStatus object, which holds the percentage complete of the task to run, and some message text set by the object user. The ProgressBarTask also owns a ProgressBar object. - Once all data is sent to the ProgressBarTask subclass (i.e. PublishTask) from the user interface class, the actual long task (such as a publishing application 28) is ready to be run. In
step 48, application task 28 is run in a separate thread II fromservlet 24, which runs in thread I. The ProgressBarTask subclass object is sent to the classes handling the long operation (publish) in that separate thread. Those classes are in charge of using the PublishTask object to set the TaskStatus that it owns with new percentages and messages when it reaches specific milestones. Instep 50, updates to task status are periodically posted to the progress bar object by progress bar task. This is the data that will be read every t seconds when an update is required. In step 52,servlet 24 sends tobrowser 32 an HTML page with progress indicator 34 (initially set to 0% completion) and a meta tag with a refresh attribute of t. In step 54,browser 32displays progress bar 34. - In
step 56, periodically, such as when an update is required to the HTML page withprogress indicator 34, the ProgressBar task takes the data from the TaskStatus object, and gives it to the ProgressBar object. The ProgressBar object uses that data to create a new HTML page to be returned instep 60 by theJava Servlet 24 tobrowser 32. Instep 60, this HTML page contains a meta tag with a refresh attribute set to a default of t seconds. This will cause in step 54 a post to theJava Servlet 24 in t seconds, causing instep 56 the user interface class (i.e. B2BCatalogPublishWizardForm) to ask the ProgressBarTask subclass to get a new HTML page from ProgressBar. The meta tag with the refresh attribute is returned instep 60 in the HTML markup until instep 58 an error in or completion oftask 26 is detected and, at that time, in step 62 the interface returns the HTML markup without the meta tag. This prevents an infinite refresh of the progress HTML page. When all updates are finished, in step 64 a button is presented on the HTML page that takes the user to another page so that he can continue with his use of the browser. - Summarizing, in this embodiment of the invention, a ProgressBarTask subclass is shared between two threads I and II. Thread I consumes the TaskStatus data from it, and user interface thread II updates it. Thread I is the user interface class which can make calls to get a new HTML page to show the user the current task status, and the thread II is the class or classes performing the
actual task 26. - The object model of
FIG. 4 and Tables I-IV illustrate how a progress indicator meta tag having a refresh attribute is used to prevent browser time-out during application execution when publishing large electronic catalog in Connect for the IBM iSeries. All objects ofFIG. 4 reside within Java servlet 24 (iSeries Connect is one Java Servlet). The Java code of Tables I-IV illustrate an exemplary embodiment of the invention for iSeries Connect. - Referring to
FIG. 4 , a class diagram illustrates progress bar task 10 (Table I), task status 12 (Table II), progress bar 14 (Table III), publish task 16 (Table IV), andapplication wizard 18. As is represented by line 11, progress bar task class 10 has aprogress bar class 14. As is represented byline 13, progress bar task class 10 has a task status class 12. As is represented byline 15, publishtask 16 extends progress bar task class 10. As is represented byline 17,application wizard class 18 has a publishtask class 16. - Progress bar task class 10 returns html to
browser 32 which containsprogress bar 34 information. Table I sets forth a Java code statement of an exemplary progress bar task class 10.TABLE I PROGRESSBAR TASK #status:TaskStatus #progressBar:ProgressBar #m_taskException:B2BCatalogExeption=null #m_trace:B2BServletTraceLogger #m_catBundle:CatalogResourceBundle #ProgressBarTask( ) #ProgressBarTask(refreshRate:int) +getProgressHTML( ):String +getProgressHTMLForError( ):String +getStatus( ):TaskStatus +getTaskException( ):B2BCatalogException +setTaskException(taskException:B2BCatalogException) - Task status class 12 contains information on how complete is thread II 26, or its error state. A Java code representation of an exemplary task status class 12 is set forth in Table II.
TABLE II TASKSTATUS −m_statusMsg:String=“” −m_percentComplete:Integer −m_onLastStep:Boolean −m_catBundle:CatalogResourceBundle +TaskStatus( ) +setTaskStatus(statusMsg:String.percentComplete:int):void +onLastStep( ):boolean statusMsg:String percentComplete:int onLastStep:boolean -
Progress bar class 14 is a data holder for the refresh rate on the meta tag ofbrowser 32, and is also used as an interface to update application task 28 thread II 26 progress. A Java code representation of an exemplaryprogress bar class 14 is set forth in Table III.TABLE III PROGRESS BAR −REFRESH_URL:String=B2BPaths.getServletURLPath( )+“/Content” −m_refreshRate:Int=5 −m_trace:B2BServletTraceLogger −m_catBundle:CatalogResourceBundle −progressHTMLStr:String +ProgressBar( ) +ProgressBar(refreshRate:int) +updateProgress(percentComplete:int,statusMsg:String, isFinalStep:boolean):String +updateProgress(percentComplete:int,statusMsg: String,errorOccurred:boolean,isFinalStep:boolean) refreshRate:Int - Publish
task class 16 is an extended class of progress bar task class 10 with specific information for application task 28 thread II 26 (what is it and what kind of data does it need.) A publish task is a subclass of progress bar task. It is needed because a publish is a long operation that needs to be monitored by a progress bar. The kind of data it needs, for example, is the catalog format that will be published, who the catalog supplier is, if it is a local or remote catalog, etc. Table IV contains a Java code representation of an exemplary publishtask class 16.TABLE IV PUBLISH TASK −m_mpFormat:MarketplaceFormat=null −m_result:PublishResult=null −m_catalog:Catalog=null −m_associateMP:B2BSupplierMarketplaceAssociationElemen... −m_priceProfiles:Vector=null −m_destination:PublishDestination=null −m_localOrRemote:int −resultsSet:Boolean −resultIsSet:Boolean −m_catBundle: CatalogResourceBundle +PublishTask(mpFormat:MarketplaceFormat) +publish(catalog:Catalog,associateMP: B2BSupplierMarketplaceAssociation) +run( ):void publishResult:PublishResult -
Application wizard class 18 is a method for starting application task 28 thread II 26. Upon completing,application wizard class 18 inducesprogress bar 34.Class 18 is a wizard that interacts with the user to obtain information on how to publish, for example, an electronic catalog. At the end of the wizard, when a finish button is clicked, publishtask class 16 is instantiated. An example of such a wizard is the B2BCatalogPublishWizardForm at - com.ibm.connect.config.B2BWizardForm.
- for the IBM iSeries Connect product, a product that allows suppliers to operate in secure market places to leverage the Internet. In publish
task class 16, the statement - +run( ):void
- is what spawns
thread II 26. - When publish
task class 16 is created, progress bar class 10 gets created as a consequence (publishtask class 16 is a sub class of progress bar task 10). When progress bar task 10 is created, task status class 12 gets created as a consequence with an initial progress state of null. In publishtask class 16, there is a run statement - +run( ):void
- that spawns application task 28 in thread II 26 (the task that will take a long time (that is, a time longer than the timeout time of client browser 32), the progress of which will be displayed in
progress bar 34.) At this point there exists a task (progress bar task 10) in application task 28 thread II 26, which has a reference to task status class 12 in a separate thread which updates task status whenever it is necessary. Bothservlet thread 24 and application task 28 have access to task status class 12, withthread 24 being the consumer andthread 26 being the maintainer of task status class 12. - Thread II 26, once spawned, sets/resets its progress bar by executing the Java code
- +setTaskStatus(statusMsg:String.percentComplete:int):void
- on the task status class 12.
- When task status class 12 is set up, no progress is complete, and a
status bar 34 with zero complete is returned toclient 30 by servlet thread I 24 which includes the metatag to refresh the page. This metatag is contained in progress bar task class 10 at - +getProgressHTML( ):String
- Application task 28 on thread II updates task status class 12, and progress bar task class 10 builds an HTML response to
client 30 showing in the statement - +getProgressHTML( ):String
- the new state of progress which had been set in task status class 12 by thread II 26 at
- +setTaskStatus(statusMsg:String.percentComplete:int):void
- That new
- +getProgressHTML( ):String
- includes a new meta tag which instructs
client 30 to refresh again in time t. - If application task 28 on thread II is 100% complete or in error state, progress bar task class 10 returns HTML without the refresh meta tag and a progress bar which shows a completion or stopped state.
- It is an advantage of the invention that there is provided a system and method for avoiding premature timeout of a browser while awaiting completion of an application.
- It will be appreciated that, although specific embodiments of the invention have been described herein for purposes of illustration, various modifications may be made without departing from the spirit and scope of the invention. In particular, it is within the scope of the invention to provide a computer program product or program element, or a program storage or memory device such as a solid or fluid transmission medium, magnetic or optical wire, tape or disc, or the like, for storing signals readable by a machine, for controlling the operation of a computer according to the method of the invention and/or to structure its components in accordance with the system of the invention.
- Further, each step of the method may be executed on any general computer, such as IBM Systems designated as zSeries, iSeries, xSeries, and pSeries, or the like and pursuant to one or more, or a part of one or more, program elements, modules or objects generated from any programming language, such as C++, Java, P1/1, Fortran or the like. And still further, each said step, or a file or object or the like implementing each said step, may be executed by special purpose hardware or a circuit module designed for that purpose.
- Accordingly, the scope of protection of this invention is limited only by the following claims and their equivalents.
Claims (5)
1. A server system for preventing time out, comprising:
a first thread executing in said server system, said first thread comprising a client interface for interfacing to a client of said server system;
a second thread executing in said server system, said second thread comprising a server application for servicing a first request by said client, wherein said client automatically times out if a response to said request is not received in said client within a pre-determined time-out period;
a task status object accessed by said server application to post completion state of said server application and by said client interface responsive to receiving a state refresh request from said client to post a state refresh response; and
wherein, responsive to receiving a state refresh request from said client, said client interface transmits a state refresh response to said client, said state refresh response comprising a completion state of said server application in generating a response to said first request and selectively including a refresh attribute instructing said client to post said state refresh request again before expiration of said pre-determined time-out period, wherein posting said state refresh request by said client responsive to said refresh attribute prevents time-out in said client, said refresh attribute being selectively included when said server application has not completed generating a response to said first request.
2. The system of claim 1 , said refresh attribute specifying a time interval for posting state refresh requests.
3. The system of claim 1 , wherein said state refresh response comprises a hypertext markup language (HTML) metatag identifying said completion state of said server application, and selectively including said refresh attribute.
4. The system of claim 1 , wherein state refresh response includes a hypertext markup language representation of a progress bar for displaying said completion state.
5. The system of claim 4 , further comprising:
a progress bar task for storing a progress bar representation of said completion state; and
a publish task responsive to said state refresh request for accessing said progress bar task for said state of completion and deriving a hypertext markup language representation of a progress bar for displaying said application state.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/931,264 US20080052351A1 (en) | 2002-04-19 | 2007-10-31 | System and method for preventing timeout of a client |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/126,484 US7330894B2 (en) | 2002-04-19 | 2002-04-19 | System and method for preventing timeout of a client |
US11/931,264 US20080052351A1 (en) | 2002-04-19 | 2007-10-31 | System and method for preventing timeout of a client |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/126,484 Continuation US7330894B2 (en) | 2002-04-19 | 2002-04-19 | System and method for preventing timeout of a client |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080052351A1 true US20080052351A1 (en) | 2008-02-28 |
Family
ID=29215038
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/126,484 Expired - Fee Related US7330894B2 (en) | 2002-04-19 | 2002-04-19 | System and method for preventing timeout of a client |
US11/931,264 Abandoned US20080052351A1 (en) | 2002-04-19 | 2007-10-31 | System and method for preventing timeout of a client |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/126,484 Expired - Fee Related US7330894B2 (en) | 2002-04-19 | 2002-04-19 | System and method for preventing timeout of a client |
Country Status (1)
Country | Link |
---|---|
US (2) | US7330894B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108268358A (en) * | 2017-12-29 | 2018-07-10 | 北京奇虎科技有限公司 | The monitoring method of task, apparatus and system |
Families Citing this family (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7493394B2 (en) * | 2003-12-31 | 2009-02-17 | Cisco Technology, Inc. | Dynamic timeout in a client-server system |
US7454434B1 (en) * | 2004-10-04 | 2008-11-18 | American Express Travel Related Services Company, Inc. | System and method for stepped loading of web page content |
US7590881B2 (en) * | 2004-10-18 | 2009-09-15 | Research In Motion Limited | Method and apparatus for controlling an upper layer in a protocol stack to delay timeouts |
EP1648141B1 (en) * | 2004-10-18 | 2006-09-13 | Research In Motion Limited | Method and Apparatus for Controlling an Upper Layer in a Protocol Stack to Delay Timeouts |
US8719363B2 (en) * | 2005-10-19 | 2014-05-06 | Adobe Systems Incorporated | Presentation of secondary local content in a region of a web page after an elapsed time |
US7774779B2 (en) * | 2005-11-18 | 2010-08-10 | At&T Intellectual Property I, L.P. | Generating a timeout in a computer software application |
US9754265B2 (en) * | 2006-05-01 | 2017-09-05 | At&T Intellectual Property I, L.P. | Systems and methods to automatically activate distribution channels provided by business partners |
GB0701916D0 (en) * | 2007-01-31 | 2007-03-14 | British Telecomm | Data transfer method |
US20090070699A1 (en) * | 2007-09-07 | 2009-03-12 | Alexis Birkill | Keeping Track of Progress Bar Position During an Extended Task in a Computer System |
US8880584B2 (en) * | 2007-12-07 | 2014-11-04 | Honeywell International, Inc. | Data transferring method and object tracking system using the same |
US9063778B2 (en) * | 2008-01-09 | 2015-06-23 | Microsoft Technology Licensing, Llc | Fair stateless model checking |
US8589946B2 (en) * | 2008-09-08 | 2013-11-19 | International Business Machines Corporation | Prevention of browser timeout |
CN101814040B (en) * | 2010-04-01 | 2013-01-09 | 北京数码视讯科技股份有限公司 | Single-thread browser and processing method thereof |
US8307031B1 (en) * | 2010-04-28 | 2012-11-06 | Google Inc. | Processing data requests using multiple request timers |
CN102377799B (en) * | 2010-08-11 | 2016-01-13 | 腾讯科技(深圳)有限公司 | Mobile phone browser server end and realize the method for the two thread mode of browser |
US8589950B2 (en) | 2011-01-05 | 2013-11-19 | Blackberry Limited | Processing user input events in a web browser |
US8941675B2 (en) | 2011-04-05 | 2015-01-27 | Blackberry Limited | Backing store memory management for rendering scrollable webpage subregions |
CN102426533B (en) * | 2011-12-12 | 2014-10-01 | 奇智软件(北京)有限公司 | Method and device for installing software |
JP5910413B2 (en) * | 2012-08-21 | 2016-04-27 | 富士通株式会社 | Information processing apparatus, activation program, and activation method |
CN110704771B (en) * | 2018-06-22 | 2024-03-01 | 北京京东尚科信息技术有限公司 | Page abnormality monitoring method, system, device, electronic equipment and readable medium |
CN110166563A (en) * | 2019-05-27 | 2019-08-23 | 杭州迪普科技股份有限公司 | A kind of page login-timeout method for updating time and device |
CN110519364A (en) * | 2019-08-23 | 2019-11-29 | 深圳前海环融联易信息科技服务有限公司 | A kind of method and its system of the high concurrent performance optimization based on jdk8 |
Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6119165A (en) * | 1997-11-17 | 2000-09-12 | Trend Micro, Inc. | Controlled distribution of application programs in a computer network |
US6205474B1 (en) * | 1998-04-14 | 2001-03-20 | Compaq Computer Corporation | Access mechanism for parallel status update for multiple servers |
US20020006603A1 (en) * | 1997-12-22 | 2002-01-17 | Bret E. Peterson | Remotely administered computer-assisted professionally supervised teaching system |
US6353853B1 (en) * | 1998-10-26 | 2002-03-05 | Triatek, Inc. | System for management of building automation systems through an HTML client program |
US6480883B1 (en) * | 1998-06-30 | 2002-11-12 | Kabushiki Kaisha Toshiba | Real-time information transmission system |
US20020169670A1 (en) * | 2001-03-30 | 2002-11-14 | Jonathan Barsade | Network banner advertisement system and method |
US20020178232A1 (en) * | 1997-12-10 | 2002-11-28 | Xavier Ferguson | Method of background downloading of information from a computer network |
US20020180795A1 (en) * | 2001-05-30 | 2002-12-05 | International Business Machines Corporation | Method, system, and program for generating a progress indicator |
US20030018887A1 (en) * | 2001-07-17 | 2003-01-23 | Dan Fishman | Method for providing user-apparent consistency in a wireless device |
US6526433B1 (en) * | 1999-12-15 | 2003-02-25 | International Business Machines Corporation | Adaptive timeout value setting for distributed computing environment (DCE) applications |
US20030046401A1 (en) * | 2000-10-16 | 2003-03-06 | Abbott Kenneth H. | Dynamically determing appropriate computer user interfaces |
US6539422B1 (en) * | 1998-05-04 | 2003-03-25 | Intermec Ip Corp. | Automatic data collection device having a network communications capability |
US20030070000A1 (en) * | 2001-09-29 | 2003-04-10 | John Coker | Computing system and method to implicitly commit unsaved data for a World Wide Web application |
US20030146932A1 (en) * | 2002-02-07 | 2003-08-07 | Jie Weng | Multi-modal synchronization |
US20030191795A1 (en) * | 2002-02-04 | 2003-10-09 | James Bernardin | Adaptive scheduling |
US20030217054A1 (en) * | 2002-04-15 | 2003-11-20 | Bachman George E. | Methods and apparatus for process, factory-floor, environmental, computer aided manufacturing-based or other control system with real-time data distribution |
US7225249B1 (en) * | 1997-09-26 | 2007-05-29 | Mci, Llc | Integrated systems for providing communications network management services and interactive generating invoice documents |
-
2002
- 2002-04-19 US US10/126,484 patent/US7330894B2/en not_active Expired - Fee Related
-
2007
- 2007-10-31 US US11/931,264 patent/US20080052351A1/en not_active Abandoned
Patent Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7225249B1 (en) * | 1997-09-26 | 2007-05-29 | Mci, Llc | Integrated systems for providing communications network management services and interactive generating invoice documents |
US6119165A (en) * | 1997-11-17 | 2000-09-12 | Trend Micro, Inc. | Controlled distribution of application programs in a computer network |
US20020178232A1 (en) * | 1997-12-10 | 2002-11-28 | Xavier Ferguson | Method of background downloading of information from a computer network |
US20020006603A1 (en) * | 1997-12-22 | 2002-01-17 | Bret E. Peterson | Remotely administered computer-assisted professionally supervised teaching system |
US6205474B1 (en) * | 1998-04-14 | 2001-03-20 | Compaq Computer Corporation | Access mechanism for parallel status update for multiple servers |
US6539422B1 (en) * | 1998-05-04 | 2003-03-25 | Intermec Ip Corp. | Automatic data collection device having a network communications capability |
US6480883B1 (en) * | 1998-06-30 | 2002-11-12 | Kabushiki Kaisha Toshiba | Real-time information transmission system |
US6353853B1 (en) * | 1998-10-26 | 2002-03-05 | Triatek, Inc. | System for management of building automation systems through an HTML client program |
US6526433B1 (en) * | 1999-12-15 | 2003-02-25 | International Business Machines Corporation | Adaptive timeout value setting for distributed computing environment (DCE) applications |
US20030046401A1 (en) * | 2000-10-16 | 2003-03-06 | Abbott Kenneth H. | Dynamically determing appropriate computer user interfaces |
US20020169670A1 (en) * | 2001-03-30 | 2002-11-14 | Jonathan Barsade | Network banner advertisement system and method |
US20020180795A1 (en) * | 2001-05-30 | 2002-12-05 | International Business Machines Corporation | Method, system, and program for generating a progress indicator |
US20030018887A1 (en) * | 2001-07-17 | 2003-01-23 | Dan Fishman | Method for providing user-apparent consistency in a wireless device |
US20030070000A1 (en) * | 2001-09-29 | 2003-04-10 | John Coker | Computing system and method to implicitly commit unsaved data for a World Wide Web application |
US20030191795A1 (en) * | 2002-02-04 | 2003-10-09 | James Bernardin | Adaptive scheduling |
US20030146932A1 (en) * | 2002-02-07 | 2003-08-07 | Jie Weng | Multi-modal synchronization |
US20030217054A1 (en) * | 2002-04-15 | 2003-11-20 | Bachman George E. | Methods and apparatus for process, factory-floor, environmental, computer aided manufacturing-based or other control system with real-time data distribution |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108268358A (en) * | 2017-12-29 | 2018-07-10 | 北京奇虎科技有限公司 | The monitoring method of task, apparatus and system |
Also Published As
Publication number | Publication date |
---|---|
US20030200255A1 (en) | 2003-10-23 |
US7330894B2 (en) | 2008-02-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20080052351A1 (en) | System and method for preventing timeout of a client | |
US6112240A (en) | Web site client information tracker | |
AU771770B2 (en) | Communication between client and server computers via HTTP, method, computer program product and system | |
EP1807771B1 (en) | Method and system for communicating and exchanging data between browser frames | |
US7559016B1 (en) | System and method for indicating web page modifications | |
JP4741153B2 (en) | Data transfer method and apparatus | |
US7925984B2 (en) | Remote configuration of intelligent software agents | |
US6557038B1 (en) | Method and apparatus for maintaining session states | |
JP3954030B2 (en) | Method and system for protecting user privacy when using applications | |
US7703019B2 (en) | Visual administrator for specifying service references to support a service | |
US20060069785A1 (en) | System and method for controlling display windows | |
US20030028608A1 (en) | Delivering electronic content | |
US7451393B1 (en) | System and method for a page rendering framework | |
JP2001014282A (en) | Device and method for information processing and medium | |
JP2007149074A (en) | Context based navigation | |
US6862620B2 (en) | Web page monitoring system and methods therefor | |
US7945550B1 (en) | System and method of managing internet browser navigation | |
US7912917B2 (en) | Persisting forms data in a composite web application environment | |
US20060031466A1 (en) | Measuring responses incurred in network transactions | |
US20080228874A1 (en) | Method and Apparatus for Collocating Application Monitoring Reports with Web Applications | |
US7721218B2 (en) | Mechanism for intelligent user interface presentation of a software agent | |
US20080133584A1 (en) | Annotation management program, device, method and annotation display program, device, method | |
US20050138136A1 (en) | Method, system and program products for updating event data on a page using code understood natively by a browser | |
US20070214110A1 (en) | Systems and methods for providing services | |
US8639804B2 (en) | Techniques for maintaining current content |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |