the present invention is a context - sensitive caching system and method . in accordance with the inventive arrangements , the context - sensitive caching system can be configured generically to cache objects across multiple contexts , for instance web pages , command execution results , database access results , application archives and audio - visual files . in particular , a common cache can be managed by a common caching engine configured to cache objects of varying contexts . advantageously , the set of objects for which the common caching engine can be configured can vary according to a set of configuration specifications for each context . in consequence , the context - sensitive caching system can provide a common cache for objects across multiple contexts , without requiring complex reprogramming typically associated with prior art caching schemes . furthermore , a shared cache namespace allows cache invalidations to occur across different application contexts . fig1 is a schematic illustration of a preferred embodiment of the context - sensitive caching system of the present invention . as shown in fig1 , the context - sensitive caching system 130 can include a common cache 170 storing cacheable objects 172 . a common caching engine 166 further can be provided in addition to a shared name generator 168 . the common caching engine 166 can identify cacheable objects 172 and can write those identified cacheable objects to the common cache 170 using a caching key generated by the shared name generator 168 . notably , plugable context providers 164 can be communicatively linked to the common caching engine 166 . each plugable context provider 164 can provide an interface to a set of configuration specifications 162 for a particular context . each configuration specification 162 , in turn , can specify those cacheable objects 172 to cache within the context , the data associated with the cacheable objects 172 which can be used to create cache keys , and rules which are to be applied when determining whether to invalidate a cacheable object 172 within the context . in one aspect of the present invention , each plugable context provider 164 can be an application exposed to the common caching engine 166 through deployment descriptors , as is well - known in the art . the plugable context provider 164 , itself , can be configured to process a uniformly formatted configuration specification 162 , for example using a markup language such as xml . still , the invention is not limited in this regard and the plugable context provider 164 can be an application exposed to the common caching engine 166 through other machine readable techniques . importantly , each configuration specification 162 which can be accessed through a plugable context provider 164 can specify not only rules for generating cache keys , but also the configuration specification 162 can specify rules for generating group cache keys for entries in the common cache 170 . in this regard , group cache keys can be used to associate a group of cache entities to a single cache key . furthermore , the configuration specification can include logical operators including and , or and not operators , which can be used in specifying the formulation of individual and group cache keys . advantageously , the plugable context provider 164 , in conjunction with the shared name generator 168 , can be configured to process the logical operators to produce the caching policy for the particular context with which the configuration specification 162 is associated . in addition to the specification of cache key generation rules , the configuration specification 162 can include rules for invalidating cache entries , whether individually or in a group , whether explicitly or otherwise . in particular , the configuration specification can specify when the validity of a cache entry has expired , or become “ stale ”, e . g . a time - to - live value . also , the configuration specification can specify when a cache entry should be explicitly invalidated based upon an extrinsic event . like the cache key generation rules , however , the plugable context provider 164 can be configured to process the invalidation rules set forth in the associated configuration specification 162 . in operation , client devices 102 a and proxy servers 102 b can be linked over computer communications network 110 to an application server 120 which hosts the context - sensitive cache 130 . the application server 120 can be a conventional application server which , for example , can respond to network requests 104 to perform an application operation with network responses 106 containing the results of the requested operations . alternatively , the application server 120 can be a database server configured to respond to database access requests with data stored therein . in any case , the application server 120 is not limited as such and can be any type of network server configured to respond to network requests 104 . the context - sensitive caching engine 130 can intercept network requests 104 to determine whether any cacheable objects 172 which are to be invoked , generated , retrieved or produced in consequence of the network requests 104 already reside in the common cache 170 . if so , the pertinent cacheable objects 172 can be retrieved from the common cache 170 rather than requiring the application server 120 to process the network request 104 . notably , as one skilled in the art will recognize , the context - sensitive caching engine 130 is not limited strictly to caching whole portions of output produced by , or work to be performed within the application server 120 . rather , the context - sensitive caching engine 130 also can cache portions of the output or work as the case may be . importantly , though fig1 illustrates the context - sensitive cache 130 as a reverse cache , the invention is not so limited . rather , the context - sensitive cache 130 further can be deployed as a client - side cache or even a proxy cache . in that regard , like the reverse cache configuration illustrated in fig1 , in a client - side or proxy cache configuration , the context - sensitive cache of the present invention advantageously can provide a common cache for objects across multiple contexts , without requiring complex reprogramming typically associated with prior art client - side and proxy caching schemes . fig2 is a flow chart illustrating a process for caching context - sensitive data in the context - sensitive caching system of fig1 . beginning in block 202 , the caching engine can receive a network request for an object . the request can be a request to retrieve an object , for example a web page or an audio - visual file . furthermore , the request can be a request for an associated application server to invoke the execution of an object , for example a method to retrieve results from a database and update the object &# 39 ; s state . finally , the request can be a request to invoke an application command . in block 204 , the common caching engine can identify the type of requested object to determine whether the requested object is cacheable . notably , the common caching engine can determine whether the requested object is cacheable based upon the configuration of the common caching engine , as specified by one or more configuration specifications driving the common caching engine . in any case , if in decision block 206 it is determined that the requested object is not a cacheable object , in block 208 the request can be forwarded on to the specified server . otherwise , the process can continue in block 210 . in block 210 , the shared name generator can consult the configuration specification associated with the identified object type to determine what data in the object or other objects as provided by the plugable context provider can be used to formulate the caching key for the object . in block 212 , the shared name generator can formulate the caching key based upon the determined data . finally , in block 214 the common caching engine can attempt to locate a cached version of the requested object in the common cache using the caching key formulated by the shared name generator . in block 216 , if the requested object is located in the common cache , the located object 218 can be retrieved from the common cache and returned to the requester . otherwise , in block 220 , the network request can be forwarded to the specified server . importantly , in block 222 , once the specified server produces the requested object , the common caching engine can determine whether to write the requested object to the common cache . in particular , the common caching engine can consult the configuration specification associated with the identified object type to determine whether the caching policy requires that the common caching engine write the requested object to the common cache . in that case , the shared name generator once again can formulate a caching key to be used when writing the requested object to the common cache . the present invention can be realized in hardware , software , or a combination of hardware and software . an implementation of the method and system of the present invention can be realized in a centralized fashion in one computer system , or in a distributed fashion where different elements are spread across several interconnected computer systems . any kind of computer system , or other apparatus adapted for carrying out the methods described herein , is suited to perform the functions described herein . a typical combination of hardware and software could be a general purpose computer system with a computer program that , when being loaded and executed , controls the computer system such that it carries out the methods described herein . the present invention can also be embedded in a computer program product , which comprises all the features enabling the implementation of the methods described herein , and which , when loaded in a computer system is able to carry out these methods . computer program or application in the present context means any expression , in any language , code or notation , of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following a ) conversion to another language , code or notation ; b ) reproduction in a different material form . significantly , this invention can be embodied in other specific forms without departing from the spirit or essential attributes thereof , and accordingly , reference should be had to the following claims , rather than to the foregoing specification , as indicating the scope of the invention .