Portable embedded local server for write-through cache

• US 8,549,101 B2
• Filed: 11/13/2009
• Issued: 10/01/2013
• Est. Priority Date: 06/16/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Mehta, Nikunj R., Swart, Garret
• Primary Examiner(s): Chan, Wing F
• Assistant Examiner(s): KATSIKIS, KOSTAS J
• Application Number:
  US12/618,654
• Publication Number:
  US 20100319054A1
• Time in Patent Office: 1,418 Days
• Field of Search: None
• US Class Current: 709/217
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

Abstract

A method of facilitating, via an embedded local server, dynamic responses to requests originating from an application and directed to a server is disclosed. An intermediary intercepts requests responds to the requests with locally stored data. The intermediary may also forward requests to an embedded local server for processing based on local data.

Claims

1. A computer-implemented process, comprising:

intercepting, at an intermediary on a first computing device, from an application running on the first computing device, a first request;

wherein the first request is a request directed to a server, and identifies;

a particular resource identifier, wherein a resource identifier identifies a resource that is remote to the first computing device; and

one or more particular methods, wherein the one or more particular methods represent actions that may be performed on a resource;

determining that the first request and an interception key of a plurality of interception keys match based on the particular resource identifier and the one or more particular methods;

wherein each interception key of the plurality of interception keys is associated with a respective embedded server on the first computing device;

in response to determining that the first request and the interception key match, relaying the first request to an embedded server associated with the interception key;

wherein the process is performed by one or more computing devices.

2. The method of claim 1, further comprising:

determining an embedded server based on the interception key;

wherein determining the embedded server comprises matching the key to an embedded server address from a plurality of embedded server addresses stored in an embedded server registry.

3. The method of claim 1, wherein at least one of the one or more particular methods of respective methods is identified by a NULL value reference.

4. The method of claim 3, wherein:

the first request is a request to retrieve or store data; and

the resource identifier indicates the data to be stored or retrieved.

5. The method of claim 4, further comprising:

the embedded server storing data in an embedded database;

receiving a second request, wherein the second request is a request to retrieve data from the server;

the embedded server responding to the second request using data stored in the embedded database;

subsequent to storing data in the embedded database, synchronizing the embedded database with the server.

6. The method of claim 5, wherein the step of synchronizing the embedded database with the server comprises determining that synchronization should occur, based, at least in part, on one or more policy criteria.

7. The method of claim 6, wherein the one or more policy criteria includes criteria related to one or more of:

time;

power consumption;

communication privacy;

network usage cost;

network availability;

conflicts caused by server contention;

or

user expressed preferences.

8. The method of claim 1, further comprising:

determining that the first request should be sent to the embedded server based at least in part on one or more policy criteria.

9. The method of claim 8, wherein the one or more policy criteria includes criteria related to one or more of:

time;

power consumption;

communication privacy;

network usage cost;

network availability;

conflicts caused by server contention;

or

user expressed preferences.

10. The method of claim 1, wherein the first computing device is a mobile computing device.

11. The method of claim 1, wherein the intermediary is a browser plugin.

12. The method of claim 1, further comprising:

storing, at an authorization registry, an authorization key, wherein the authorization key represents an authorization condition associated with the interception key;

receiving, from the embedded server, a response to the first request;

wherein the response to the first request is based, at least in part, on whether or not the authorization condition has been satisfied.

13. The method of claim 12, further comprising:

based on a determination that the authorization condition is no longer satisfied;

removing the authorization key from an authorization registry; and

removing the interception key from an interception key registry.

14. The method of claim 1, further comprising:

the embedded server revising an interception key registry, wherein the step of revising the interception key registry comprises at least one of the following;

changing a key in the interception key registry;

adding a key to the interception key registry; and

removing a key from the interception key registry.

15. A computer-implemented method, comprising:

intercepting, at an intermediary on a first computing device, from an application running on the first computing device, a first request;

wherein the first request is a request directed to a server, and identifies;

a particular resource identifier, wherein a resource identifier identifies a resource that is remote to the first computing device; and

one or more particular methods, wherein the one or more particular methods represent actions that may be performed on a resource;

determining that the first request and an interception key of a plurality of interception keys match based on the particular resource identifier and the one or more particular methods;

wherein each interception key of the plurality of interception keys is associated with a respective embedded server on the first computing device, and is associated with;

a respective resource identifier; and

one or more references to respective methods, wherein the respective methods represent actions that may be performed on a resource;

relaying the first request to the server;

receiving, from the server, a first response to the first request;

relaying the first response to an embedded server associated with the interception key;

the embedded server, based on a determination made from analyzing the first response, causing first data associated with the first response to be stored;

wherein the process is performed by one or more computing devices.

16. The method of claim 15, further comprising:

intercepting, at the intermediary, a second request, wherein the second request is directed to the server and includes the first resource identifier;

based at least in part on the interception key, the intermediary determining that the request can be satisfied with the first data;

the intermediary responding to the second request using first data.

17. The method of claim 15, further comprising:

determining that the first request should be relayed to the embedded server based at least in part on one or more policy criteria.

18. The method of claim 17, wherein the one or more policy criteria includes criteria related to one or more of:

time;

power consumption;

communication privacy;

network usage cost;

network availability;

conflicts caused by server contention;

or

user expressed preferences.

19. The method of claim 15, further comprising:

the embedded server revising an interception key registry, wherein the step of revising the interception key registry comprises at least one of the following;

changing a key in the interception key registry;

adding a key to the interception key registry; and

removing a key from the interception key registry.

20. One or more non-transitory computer-readable media storing instructions, which, when executed by one or more processors, cause one or more computing devices to perform operations comprising:

intercepting, at an intermediary on a first computing device, from an application running on the first computing device, a first request;

wherein the first request is a request directed to a server, and identifies;

a particular resource identifier, wherein a resource identifier identifies a resource that is remote to the first computing device; and

one or more particular methods, wherein the one or more particular methods represent actions that may be performed on a resource;

determining that the first request and an interception key of a plurality of interception keys match based on the particular resource identifier and the one or more particular methods;

wherein each interception key of the plurality of interception keys is associated with a respective embedded server on the first computing device;

in response to determining that the first request and the interception key match, relaying the first request to an embedded server associated with the interception key.

21. The non-transitory computer-readable media of claim 20, the operations further comprising:

determining the embedded server based on the interception key;

wherein determining the embedded server comprises matching the interception key to an embedded server address from a plurality of embedded server addresses stored in an embedded server registry.

22. The non-transitory computer-readable media of claim 20, wherein at least one of the one or more particular methods or respective methods is identified by a NULL value reference.

23. The non-transitory computer-readable media of claim 22, wherein:

the first request is a request to retrieve or store data; and

the particular resource identifier indicates the data to be stored or retrieved.

24. The non-transitory computer-readable media of claim 23, the operations further comprising:

the embedded server storing data in an embedded database;

receiving a second request, wherein the second request is a request to retrieve data from the server;

the embedded server responding to the second request using data stored in the embedded database;

subsequent to storing data in the embedded database, synchronizing the embedded database with the server.

25. The non-transitory computer-readable media of claim 24, wherein the step of synchronizing the embedded database with the server comprises determining that synchronization should occur, based, at least in part, on one or more policy criteria.

26. The non-transitory computer-readable media of claim 25, wherein the one or more policy criteria includes criteria related to one or more of:

time;

power consumption;

communication privacy;

network usage cost;

network availability;

conflicts caused by server contention;

or user expressed preferences.

27. The non-transitory computer-readable media of claim 20, the operations further comprising:

determining that the first request should be sent to the embedded server based at least in part on one or more policy criteria.

28. The non-transitory computer-readable media of claim 27, wherein the one or more policy criteria includes criteria related to one or more of:

time;

power consumption;

communication privacy;

network usage cost;

network availability;

conflicts caused by server contention;

or user expressed preferences.

29. The non-transitory computer-readable media of claim 20, wherein the first computing device is a mobile computing device.

30. The non-transitory computer-readable media of claim 20, wherein the intermediary is a browser plugin.

31. The non-transitory computer-readable media of claim 20, the operations further comprising:

storing, at an authorization registry, an authorization key, wherein the authorization key represents an authorization condition associated with the interception key;

receiving, from the embedded server, a response to the first request;

wherein the response to the first request is based, at least in part, on whether or not the authorization condition has been satisfied.

32. The non-transitory computer-readable media of claim 31, the operations further comprising:

based on a determination that the authorization condition is no longer satisfied;

removing the authorization key from the authorization registry; and

removing the interception key from an interception key registry.

33. The non-transitory computer-readable media of claim 20, the operations further comprising:

the embedded server revising an interception key registry, wherein the step of revising the interception key registry comprises at least one of the following;

changing a key in the interception key registry;

adding a key to the interception key registry; and

removing a key from the interception key registry.

34. One or more non-transitory computer-readable media storing instructions, which, when executed by one or more processors, cause one or more computing devices to perform operations comprising:

intercepting, at an intermediary on a first computing device, from an application running on the first computing device, a first request;

wherein the first request is a request directed to a server, and identifies;

a particular resource identifier, wherein a resource identifier identifies a resource that is remote to the first computing device; and

one or more particular methods, wherein the one or more particular methods represent actions that may be performed on a resource;

determining that the first request and an interception key of a plurality of interception keys match based on the particular resource identifier and the one or more particular methods;

wherein each interception key of the plurality of interception keys is associated with a respective embedded server on the first computing device, and is associated with;

a respective resource identifier; and

one or more references to respective methods, wherein the respective methods represent actions that may be performed on a resource;

relaying the first request to the server;

receiving, from the server, a first response to the first request;

relaying the first response to an embedded server associated with the interception key;

the embedded server, based on a determination made from analyzing the first response, causing first data associated with the first response to be stored.

35. The non-transitory computer-readable media of claim 34, the operations further comprising:

intercepting, at the intermediary, a second request, wherein the second request is directed to the server and includes the particular resource identifier;

based at least in part on the interception key, the intermediary determining that the second request can be satisfied with the first data;

the intermediary responding to the second request using first data.

36. The non-transitory computer-readable media of claim 34, the operations further comprising:

determining that the first request should be relayed to the embedded server based at least in part on one or more policy criteria.

37. The non-transitory computer-readable media of claim 36, wherein the one or more policy criteria includes criteria related to one or more of:

time;

power consumption;

communication privacy;

network usage cost;

network availability;

conflicts caused by server contention;

or user expressed preferences.

38. The non-transitory computer-readable media of claim 34, the operations further comprising:

the embedded server revising an interception key registry, wherein the step of revising the interception key registry comprises at least one of the following;

changing a key in the interception key registry;

adding a key to the interception key registry; and

removing a key from the interception key registry.