OK. I think I finaly get the architecture. From a user's perspective it is all server side. From Fuseki's perspective the cache may be remotly hosted.
Sometimes I think we need more diagrams. Thx, Claude On Fri, Jan 23, 2015 at 3:34 PM, Saikat Maitra <saikat.mai...@gmail.com> wrote: > The remote cache instances will be the memcache or couchbase buckets based > on user configuration. > Fuseki will use CacheStore which in turn will fetch the cache data from > remote cache buckets and set data if cache buckets do not have data. > > I have also look into the following issue related to Fuseki responses and > will take it up once I complete this jira issue. > > https://issues.apache.org/jira/browse/JENA-388 > > Regards > Saikat > > > On Fri, Jan 23, 2015 at 8:37 PM, Claude Warren <cla...@xenei.com> wrote: > > > So if local is on the server then remote must be on the client? Or are > you > > talking about adding proper caching headers to Fuseki requests? > > > > On Fri, Jan 23, 2015 at 3:05 PM, Saikat Maitra <saikat.mai...@gmail.com> > > wrote: > > > > > Hello Claude, > > > > > > The In memory local cache will have provision to use guava libraries > > caches > > > and it will be in server side. > > > > > > Regards > > > Saikat > > > > > > > > > > > > On Fri, Jan 23, 2015 at 6:39 PM, Claude Warren <cla...@xenei.com> > wrote: > > > > > > > In memory local? > > > > > > > > Does this mean you are looking at client side caching? > > > > > > > > The rest make sense to me. > > > > > > > > On Fri, Jan 23, 2015 at 12:08 PM, Saikat Maitra < > > saikat.mai...@gmail.com > > > > > > > > wrote: > > > > > > > > > Hello Claude, Andy, > > > > > > > > > > In reference to your email I would like to discuss the way I am > > looking > > > > > forward to implement the Cache Layer. > > > > > > > > > > 1. We will be creating a global cache store based on config params > > > passed > > > > > via cache.properties. > > > > > 2. Users will have option to select any of the following cache > store > > as > > > > > default > > > > > a) In memory local cache > > > > > b) remote in memory cache > > > > > c) remote in memory cache with persistence in disk > > > > > 3. We will update SPARQL_QUERY to read query results from cache if > > > > > available and if the ResultSet is within valid time to live. > > > > > 4. If cache has expired we will run executeQuery and repopulate the > > > cache > > > > > with updated time to live. > > > > > 5. We will add Tests to validate different cache store operations. > > > > > 6. I am still evaluating the changes required to accommodate > > different > > > > > datasets. > > > > > > > > > > Please let me know if there are changes required in the > > implementation. > > > > > > > > > > Regards > > > > > Saikat > > > > > > > > > > On Fri, Jan 23, 2015 at 3:58 PM, Claude Warren (JIRA) < > > j...@apache.org > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > [ > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289054#comment-14289054 > > > > > > ] > > > > > > > > > > > > Claude Warren commented on JENA-626: > > > > > > ------------------------------------ > > > > > > > > > > > > The security layer needs the ability to disable caching for > > specific > > > > > > models. > > > > > > > > > > > > If security is in play then caching needs to be by user. (though > > > there > > > > > are > > > > > > probably cases for by user group memebership and the like) > Perhaps > > > > what > > > > > is > > > > > > needed is for the query engine to specify if the result may be > > > cached. > > > > > > Since the secure models have their own query engine > implementation > > > that > > > > > > query engine can specify if the query may be cached. > > > > > > > > > > > > Query engines that are querying composit graphs may have some > > issues > > > > with > > > > > > this as some of the graphs may be secure. > > > > > > > > > > > > Claude > > > > > > > > > > > > > SPARQL Query Caching > > > > > > > -------------------- > > > > > > > > > > > > > > Key: JENA-626 > > > > > > > URL: > > > https://issues.apache.org/jira/browse/JENA-626 > > > > > > > Project: Apache Jena > > > > > > > Issue Type: Improvement > > > > > > > Reporter: Andy Seaborne > > > > > > > Labels: gsoc, java, linked_data, rdf, sparql > > > > > > > > > > > > > > Add a caching layer to Fuseki to cache the results of SPARQL > > Query > > > > > > requests. This cache should allow for in-memory and disk-based > > > > caching, > > > > > > configuration and cache management, and coordination with data > > > > > modification. > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > This message was sent by Atlassian JIRA > > > > > > (v6.3.4#6332) > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > I like: Like Like - The likeliest place on the web > > > > <http://like-like.xenei.com> > > > > LinkedIn: http://www.linkedin.com/in/claudewarren > > > > > > > > > > > > > > > -- > > I like: Like Like - The likeliest place on the web > > <http://like-like.xenei.com> > > LinkedIn: http://www.linkedin.com/in/claudewarren > > > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
