OFFLINE APPLICATION SUPPORT

• US 20140067849A1
• Filed: 08/29/2012
• Published: 03/06/2014
• Est. Priority Date: 08/29/2012
• Status: Active Grant

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: entIT Software LLC (Open Text Corporation)
• Inventors: Belinsky, Ofer, Greenberg, Nadav, Shachar, Yaniv, Mei-Raz, Alon
• Granted Patent: US 9,483,576 B2
• Time in Patent Office: Days
• US Class Current: 707/769
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

An offline support system operates to record a plurality of request/response pairs exchanged between an application and a web service. The system determines if a current request from the application can be communicated to the web service. Upon a positive determination, the current request is passed to the web service. Upon a negative determination, a most recent recorded request/response pair having a request matching the current request is identified. The response from the identified pair is passed to the application as if it were a response to the current request.

Claims

1. An offline application support system comprising a non-transitory computer readable resource storing instructions, that when executed, cause a processing resource to:

record a plurality of request/response pairs exchanged between the application and a web service;

determine if a current request from the application can be communicated to the web service;

upon a positive determination, passing the current request to the web service; and

upon a negative determination, identifying a most recent recorded request/response pair having a request matching the current request and passing the response from the identified pair to the application as if it were a response to the current request.

2. The system of claim 1, wherein passing comprises passing the prior response to the mobile application as if it were a response from the current request returned from the web service and cause a display that indicates information being presented by the application may not be current, the information corresponding to the prior response.

3. The system of claim 1, wherein the instructions, when executed, cause the processing resource to:

examine the current request for an exception indicator; and

upon the determination that a current request from the application cannot be communicated to the web service, pass the current request to an exception handler rather than obtaining and passing the response from the identified pair to the application if the exception indicator is found in the current request.

4. The system of claim 3, wherein recording comprises recording the plurality of request/response pairs in a repository searchable using a current request from the application to the web service as a key, upon a positive determination, updating the repository to include a request response pair for the current request and its corresponding response.

5. The system of claim 4 wherein the instructions, when executed, cause the processing resource to, upon the negative determination, utilize the current request as a key to search for a request response pair and, if a pair cannot be found, pass the current request to an exception handler.

6. The system of claim 1, further comprising the processing resource.

7. A system comprising a status engine and a record engine, wherein:

the status engine is configured to determine if a current application request can be communicated from a mobile device to a web service and upon a negative determination obtain a previously recorded response to a prior request matching the current request and passing the previously recorded response to the mobile application as if it were a response to the current request; and

the record engine is configured to, following a positive determination by the status engine, record the current request and its corresponding response such that status engine can later return that response as a response to a future request from the mobile application as if it were a response to the future request.

8. The system of claim 7, comprising an interface engine configured, upon the negative determination by the status engine, to cause a display that indicates information being presented by the mobile application may not be current, the information corresponding to the prior response.

9. The system of claim 7, comprising an exception engine configured to take an action with response to a current request that does not include passing a prior response to the mobile application, and wherein:

the status engine is configured to, upon the determination that a current request from the mobile application cannot be communicated to the web service, pass the current request to the exception engine rather than obtain and pass the prior response to the mobile application if the current request includes an exception indicator.

10. The system of claim 7, wherein:

the record engine is configured to record request/response pairs exchanged between the mobile application and the web service in a repository searchable using a current request from the application to the web service as a key; and

the status engine is configured to obtain the prior response by using the current request as a key for use in identifying a most recent request/response pair in the repository having a request matching the key.

11. An offline support method for a mobile application, comprising:

maintaining a repository of request/response pairs exchanged between a mobile applications and a web service; and

upon a determination that a current request from the mobile application cannot be communicated to the web service, obtaining a prior response from a pair in the repository, the pair including a past request matching the current request, passing the prior response to the mobile application as if it were a response from the current request returned from the web service.

12. The method of claim 11, wherein passing comprises passing the prior response to the mobile application as if it were a response from the current request returned from the web service and causing a display that indicates information being presented by the mobile application may not be current, the information corresponding to the prior response.

13. The method of claim 11, comprising upon a determination that the current request can be communicated to the web service, updating the repository to include a request response pair for the current request and a response from the web service to the current request.

14. The method of claim 13, the comprising causing a display that indicates that information being presented by the mobile application is current, the information corresponding to a response to the current request received from the web service.

15. The method of claim 11, comprising:

examining the current request for an exception indicator; and

upon the determination that a current request from the mobile application cannot be communicated to the web service, passing the current request to an exception handler rather than obtaining and passing the prior response to the mobile application if the exception indicator is found.