MULTI-LEVEL ADAPTIVE CACHING WITHIN ASSET-BASED WEB SYSTEMS

• US 20130013729A1
• Filed: 07/07/2011
• Published: 01/10/2013
• Est. Priority Date: 07/07/2011
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bennett, Jonathan D.
• Granted Patent: US 8,914,466 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/2876 Pairs of inter-processing entities at each side of the network, e.g. split proxies
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5683 Storage of data provided by user terminals, i.e. reverse caching

Abstract

A server monitors receipt of application access requests for application asset data from client devices. Each client device includes a local cache and the server includes a back-end cache. In response to receipt of each application access request, a number of client devices requesting access to the application asset data and an access privilege type requested by each requesting client device are determined The application asset data is migrated between the back-end cache and at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device.

Claims

1. A method, comprising:

monitoring, via a server comprising a back-end cache, received application access requests for application asset data from client devices that each comprise a local cache;

determining, in response to each received application access request, a number of the client devices requesting access to the application asset data and an access privilege type requested by each requesting client device; and

migrating the application asset data between the back-end cache and at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device.

2. The method of claim 1, where:

monitoring, via the server comprising the back-end cache, the received application access requests for the application asset data from the client devices that each comprise the local cache comprises receiving a first application access request comprising a write-access privilege type from a first client device;

determining, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device comprises determining that the number of client devices requesting access to the application asset data comprises one client device and that the access privilege type requested by the first client device comprises the write-access privilege type; and

migrating the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device comprises;

assigning ownership of the application asset data to the first client device; and

sending the application asset data from the back-end cache of the server to the local cache of the first client device based upon determining that the number of client devices requesting access to the application asset data comprises one client device and determining that the access privilege type requested by the first client device comprises the write-access privilege type.

3. The method of claim 2, where:

monitoring, via the server comprising the back-end cache, the received application access requests for the application asset data from the client devices that each comprise the local cache comprises receiving a second application access request comprising the write-access privilege type from a second client device;

determining, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device comprises determining that the number of client devices requesting access to the application asset data comprises two client devices and that the access privilege type requested by each of the first client device and the second client device comprises the write-access privilege type; and

migrating the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device comprises;

assigning ownership of the application asset data to the server; and

sending the application asset data from the local cache of the first client device to the back-end cache of the server in response to determining that the number of client devices requesting access to the application asset data comprises two client devices and determining that the access privilege type requested by each of the first client device and the second client device comprises the write-access privilege type.

4. The method of claim 2, where assigning ownership of the application asset data to the first client device comprises assigning ownership of the application asset data to the first client device within an application access lookup table maintained by the server within the back-end cache.

5. The method of claim 1, where:

monitoring, via the server comprising the back-end cache, the received application access requests for the application asset data from the client devices that each comprise the local cache comprises receiving at least two application access requests each comprising a read-only access privilege type from at least two client devices;

determining, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device comprises determining that the number of client devices requesting access to the application asset data comprises the at least two client devices and that the access privilege type requested by the at least two client devices comprises the read-only access privilege type; and

migrating the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device comprises;

maintaining ownership of the application asset data by the server; and

sending the application asset data to the local cache of the at least two client devices in response to determining that the number of client devices requesting access to the application asset data comprises the at least two client devices and that the access privilege type requested by the at least two client devices comprises the read-only access request type.

6. The method of claim 5, where:

monitoring, via the server comprising the back-end cache, the received application access requests for the application asset data from the client devices that each comprise the local cache comprises receiving an additional application access request comprising a write-access privilege type from an additional client device;

determining, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device comprises determining that the number of client devices requesting access to the application asset data comprises multiple client devices and that the access privilege type requested by at least one of the multiple client devices comprises the write-access privilege type; and

migrating the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device comprises;

maintaining ownership of the application asset data by the server; and

instructing each of the at least two client devices and the additional client device to access the application asset data within the back-end cache of the server in response to determining that the number of client devices requesting access to the application asset data comprises the multiple client devices and that the access privilege type requested by the at least one of the multiple client devices comprises the write-access privilege type.

7. The method of claim 6, where monitoring, via the server comprising the back-end cache, the received application access requests for the application asset data from the client devices that each comprise the local cache comprises receiving an application asset data change from the additional client device, and further comprising:

updating the application asset data stored within the back-end cache of the server with the application asset data change; and

persisting the updated application asset data to a database.

8. The method of claim 7, further comprising broadcasting the application asset data change to the at least two client devices from which the at least two application access data requests, each comprising the read-only access privilege type, were received.

9. A server apparatus, comprising:

a back-end cache; and

a processor programmed to;

monitor received application access requests for application asset data from client devices that each comprise a local cache;

determine, in response to each received application access request, a number of the client devices requesting access to the application asset data and an access privilege type requested by each requesting client device; and

migrate the application asset data between the back-end cache and at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device.

10. The server apparatus of claim 9, where, in being programmed to:

monitor the received application access requests for the application asset data from the client devices that each comprise the local cache, the processor is programmed to receive a first application access request comprising a write-access privilege type from a first client device;

determine, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the processor is programmed to determine that the number of client devices requesting access to the application asset data comprises one client device and that the access privilege type requested by the first client device comprises the write-access privilege type; and

migrate the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the processor is programmed to;

assign ownership of the application asset data to the first client device; and

send the application asset data from the back-end cache to the local cache of the first client device based upon determining that the number of client devices requesting access to the application asset data comprises one client device and determining that the access privilege type requested by the first client device comprises the write-access privilege type.

11. The server apparatus of claim 10, where, in being programmed to:

monitor the received application access requests for the application asset data from the client devices that each comprise the local cache, the processor is programmed to receive a second application access request comprising the write-access privilege type from a second client device;

determine, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the processor is programmed to determine that the number of client devices requesting access to the application asset data comprises two client devices and that the access privilege type requested by each of the first client device and the second client device comprises the write-access privilege type; and

migrate the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the processor is programmed to;

assign ownership of the application asset data to the server apparatus; and

send the application asset data from the local cache of the first client device to the back-end cache in response to determining that the number of client devices requesting access to the application asset data comprises two client devices and determining that the access privilege type requested by each of the first client device and the second client device comprises the write-access privilege type.

12. The server apparatus of claim 10, where, in being programmed to assign ownership of the application asset data to the first client device, the processor is programmed to assign ownership of the application asset data to the first client device within an application access lookup table maintained within the back-end cache.

13. The server apparatus of claim 9, where, in being programmed to:

monitor the received application access requests for the application asset data from the client devices that each comprise the local cache, the processor is programmed to receive at least two application access requests each comprising a read-only access privilege type from at least two client devices;

determine, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the processor is programmed to determine that the number of client devices requesting access to the application asset data comprises the at least two client devices and that the access privilege type requested by the at least two client devices comprises the read-only access privilege type; and

migrate the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the processor is programmed to;

maintain ownership of the application asset data; and

send the application asset data to the at least two client devices in response to determining that the number of client devices requesting access to the application asset data comprises the at least two client devices and that the access privilege type requested by the at least two client devices comprises the read-only access request type.

14. The server apparatus of claim 13, where, in being programmed to:

monitor the received application access requests for the application asset data from the client devices that each comprise the local cache, the processor is programmed to receive an additional application access request comprising a write-access privilege type from an additional client device;

determine, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the processor is programmed to determine that the number of client devices requesting access to the application asset data comprises multiple client devices and that the access privilege type requested by at least one of the multiple client devices comprises the write-access privilege type; and

migrate the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the processor is programmed to;

maintain ownership of the application asset data; and

instruct each of the at least two client devices and the additional client device to access the application asset data within the back-end cache in response to determining that the number of client devices requesting access to the application asset data comprises the multiple client devices and that the access privilege type requested by the at least one of the multiple client devices comprises the write-access privilege type.

15. The server apparatus of claim 14, further comprising a database;

and

where, in being programmed to monitor the received application access requests for the application asset data from the client devices that each comprise the local cache, the processor is programmed to receive an application asset data change from the additional client device, and the processor is further programmed to;

update the application asset data stored within the back-end cache with the application asset data change; and

persist the updated application asset data to a database.

16. The server apparatus of claim 15, where the processor is further programmed to broadcast the application asset data change to the at least two client devices from which the at least two application access data requests, each comprising the read-only access privilege type, were received.

17. A computer program product comprising a computer readable storage medium including computer readable program code, where the computer readable program code when executed on a computer causes the computer to:

monitor, via a server comprising a back-end cache, received application access requests for application asset data from client devices that each comprise a local cache;

determine, in response to each received application access request, a number of the client devices requesting access to the application asset data and an access privilege type requested by each requesting client device; and

migrate the application asset data between the back-end cache and at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device.

18. The computer program product of claim 17, where, in causing the computer to:

monitor, via the server comprising the back-end cache, the received application access requests for the application asset data from the client devices that each comprise the local cache, the computer readable program code when executed on the computer causes the computer to receive a first application access request comprising a write-access privilege type from a first client device;

determine, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the computer readable program code when executed on the computer causes the computer to determine that the number of client devices requesting access to the application asset data comprises one client device and that the access privilege type requested by the first client device comprises the write-access privilege type; and

migrate the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the computer readable program code when executed on the computer causes the computer to;

assign ownership of the application asset data to the first client device; and

send the application asset data from the back-end cache of the server to the local cache of the first client device based upon determining that the number of client devices requesting access to the application asset data comprises one client device and determining that the access privilege type requested by the first client device comprises the write-access privilege type.

19. The computer program product of claim 18, where, in causing the computer to:

monitor, via the server comprising the back-end cache, the received application access requests for the application asset data from the client devices that each comprise the local cache, the computer readable program code when executed on the computer causes the computer to receive a second application access request comprising the write-access privilege type from a second client device;

determine, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the computer readable program code when executed on the computer causes the computer to determine that the number of client devices requesting access to the application asset data comprises two client devices and that the access privilege type requested by each of the first client device and the second client device comprises the write-access privilege type; and

migrate the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the computer readable program code when executed on the computer causes the computer to;

assign ownership of the application asset data to the server; and

send the application asset data from the local cache of the first client device to the back-end cache of the server in response to determining that the number of client devices requesting access to the application asset data comprises two client devices and determining that the access privilege type requested by each of the first client device and the second client device comprises the write-access privilege type.

20. The computer program product of claim 18, where, in causing the computer to assign ownership of the application asset data to the first client device, the computer readable program code when executed on the computer causes the computer to assign ownership of the application asset data to the first client device within an application access lookup table maintained by the server within the back-end cache.

21. The computer program product of claim 17, where, in causing the computer to:

monitor, via the server comprising the back-end cache, the received application access requests for the application asset data from the client devices that each comprise the local cache, the computer readable program code when executed on the computer causes the computer to receive at least two application access requests each comprising a read-only access privilege type from at least two client devices;

determine, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the computer readable program code when executed on the computer causes the computer to determine that the number of client devices requesting access to the application asset data comprises the at least two client devices and that the access privilege type requested by the at least two client devices comprises the read-only access privilege type; and

migrate the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the computer readable program code when executed on the computer causes the computer to;

maintain ownership of the application asset data by the server; and

send the application asset data to the local cache of the at least two client devices in response to determining that the number of client devices requesting access to the application asset data comprises the at least two client devices and that the access privilege type requested by the at least two client devices comprises the read-only access request type.

22. The computer program product of claim 21, where, in causing the computer to:

monitor, via the server comprising the back-end cache, the received application access requests for the application asset data from the client devices that each comprise the local cache, the computer readable program code when executed on the computer causes the computer to receive an additional application access request comprising a write-access privilege type from an additional client device;

determine, in response to each received application access request, the number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the computer readable program code when executed on the computer causes the computer to determine that the number of client devices requesting access to the application asset data comprises multiple client devices and that the access privilege type requested by at least one of the multiple client devices comprises the write-access privilege type; and

migrate the application asset data between the back-end cache and the at least one local cache based upon the determined number of client devices requesting access to the application asset data and the access privilege type requested by each requesting client device, the computer readable program code when executed on the computer causes the computer to;

maintain ownership of the application asset data by the server; and

instruct each of the at least two client devices and the additional client device to access the application asset data within the back-end cache of the server in response to determining that the number of client devices requesting access to the application asset data comprises the multiple client devices and that the access privilege type requested by the at least one of the multiple client devices comprises the write-access privilege type.

23. The computer program product of claim 22, where, in causing the computer to monitor, via the server comprising the back-end cache, the received application access requests for the application asset data from the client devices that each comprise the local cache, the computer readable program code when executed on the computer causes the computer to receive an application asset data change from the additional client device, and the computer readable program code when executed on the computer further causes the computer to:

update the application asset data stored within the back-end cache of the server with the application asset data change; and

persist the updated application asset data to a database.

24. The computer program product of claim 23, where the computer readable program code when executed on the computer further causes the computer to broadcast the application asset data change to the at least two client devices from which the at least two application access data requests, each comprising the read-only access privilege type, were received.