incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henry Story (JIRA)" <>
Subject [jira] [Commented] (CLEREZZA-540) GraphNode provider service
Date Sat, 21 May 2011 16:38:47 GMT


Henry Story commented on CLEREZZA-540:

I think I meant the WebProxy which has been deleted here and moved elsewhere.

So clearly this is something that has arisen out of the need for a WebProxy. The WebProxy
was made into a TcProvider, in issue
CLEREZZA-531 after a long debate linked to there on what the names of graphs should be. It
seems that this ad-hoc graph naming is leading to this spagetti monster here which checks
the following providers:

- UserManager: the only implementation of UserManager requires a TcManager
- WebIdGraphsService: also requires a TcManager
- PlatformConfig: requires TcManager
- ContentGraphProvider: requires TcManager
- TcManager

So it looks like each time we create a new object type we are going to increase the if-then
statements in this class.

> GraphNode provider service
> --------------------------
>                 Key: CLEREZZA-540
>                 URL:
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Reto Bachmann-Gmür
>            Assignee: Reto Bachmann-Gmür
>              Labels: platform, rdf
> Implement a platform service that returns GraphNodes for URIs. The GraphNode is the resource
identified by that uri with as BaseGraph sources considered authoritative for that resource.
> Note: it ois left to possible subsequent issues to connect this to the ability manually
refresh caches pertinent to a resource  on demand.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message