jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Woonsan Ko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-4354) VFS (commons-vfs) based Persistence Manager
Date Mon, 06 Aug 2018 15:05:00 GMT

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

Woonsan Ko commented on JCR-4354:
---------------------------------

I'd like to provide PR(s) for this improvement some day. Thanks!

> VFS (commons-vfs) based Persistence Manager
> -------------------------------------------
>
>                 Key: JCR-4354
>                 URL: https://issues.apache.org/jira/browse/JCR-4354
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>            Reporter: Woonsan Ko
>            Priority: Major
>
> I think it would be nice to have a VFS (commons-vfs) based {{Persistence Manager}}.
> For example, I have worked with a Jackrabbit based WCMS product which recommends using
one of {{BundleDbPersistenceManager}} components for both workspaces and version for clustering.
> One typical problem is that the version storage in DBMS keeps increasing a lot, so as
a result we've recommended cleaning up older version items periodically. (You may google "cms
version cleaner" for more info.)
> In this case, if they were able to configure a VFS based Persistence Manager for the
versions, their DB size would keep small enough, and they may keep the version items almost
infinitely.
> And, another possible use case is that some people may use VFS based PersistenceManager
for both workspaces and version, backed by a clustered WebDAV server or SFTP server. That
could help increase architectural options as well. Also, they can use VFS-based DataStore
provided by JCR-3975.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message