incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CLEREZZA-525) Refactory Werbproxy
Date Sun, 15 May 2011 01:10:47 GMT

    [ https://issues.apache.org/jira/browse/CLEREZZA-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033622#comment-13033622
] 

Reto Bachmann-Gmür commented on CLEREZZA-525:
---------------------------------------------

Added a new project with WebProxy in package org.apache.clerezza.rdf.storage.web. This exposed
both a WebProxy service as well as a regulat WeightedTcManager. Cleint applications that do
not wont to force a particular CacheUpdatePolicy should not use this interface but rather
access all TripleCollections via TcManager. Only clients that want to enforce an update policy
should access the org.apache.clerezza.rdf.storage.web.WebProxy service.

TODO: We should provide a virtual graph from which meta information about the cached graphs
can be retrieved. E.g. time of last retrieval, connection security, etc.

> Refactory Werbproxy
> -------------------
>
>                 Key: CLEREZZA-525
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-525
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Reto Bachmann-Gmür
>            Assignee: Reto Bachmann-Gmür
>
> The current api has many undocumented public methods and it seems to make an unsharp
distinction between the caching (and respective access) of graphs and of graphnodes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message