Summary: | [prov] should rollback repo be a registered service? | ||
---|---|---|---|
Product: | [Eclipse Project] Equinox | Reporter: | Susan McCourt <susan> |
Component: | Incubator | Assignee: | equinox.incubator-inbox <equinox.incubator-inbox> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | jeffmcaffer, john.arthorne, pascal |
Version: | 3.4 | Keywords: | api |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Susan McCourt
2007-12-03 15:24:47 EST
An interesting thing that has been lurking in the back of my mind is making all the repo into services... Didn't mean to broaden this particular bug but it feels strange to call out one in particular. I was thinking about this when we first talked about the idea. However it seems that this would go against the API changes John are working on in the repository manager area. The other approach we could take to make the repo available is to publish well known keys for some repositories. It needn't be the actual IMetadataRepository object registered as a service, because that would prevent us from discarding the large repository objects when not in use. However, we could instead register a service object capable of returning a repository, or providing a repository location. In fact, we could just register an instance of the Location service for each repository and publish the service filter in API. Leave as it is for now. This is consistent with the other repository locations we make available on AgentLocation. There is an API method for obtaining the repository location, but the actual repository object is still obtained via a service call. |