[
https://issues.apache.org/jira/browse/JCR-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649043#action_12649043
]
Jukka Zitting commented on JCR-1865:
------------------------------------
-1 Why should we put the client be in control of a server process like garbage
collection? I would prefer a configuration option, a user interface in
jackrabbit-webapp, or perhaps a JMX bean for such purposes. See also the
related discussions about the shutdown method and the proposed cluster sync
method.
If we really do need to expose this in a client API, I'm with Felix in
preferring to hide the implementation details and make this just a single
no-argument method like JackrabbitSesssion.gc().
> Add the Data Store to the Jackrabbit API
> ----------------------------------------
>
> Key: JCR-1865
> URL: https://issues.apache.org/jira/browse/JCR-1865
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Minor
> Attachments: api.patch, core.patch
>
>
> Currently, the garbage collection is not part of the Jackrabbit API. However,
> the data store garbage collection must be used once in a while if the data
> store is enabled. I propose to add the required interfaces to the Jackrabbit
> API. This will also allow to call garbage collection using RMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
