23 Nov
2010
23 Nov
'10
8:41 p.m.
Le 23 nov. 2010 à 19:29, Caleb James DeLisle a écrit :
Leave it open by allowing hooks.
I think the interest here is to integrate in existing infrastructure an entreprise already
has.
svn is one fair leader there.
Well, mounting is a "root-like" operation.
Opening a VFS to some server would be something that a configurator of XWiki could be
doing.
How do you manage version in there? With an attic like in CVS?
paul
I would like
to suggest you also an svn based storage if that is conceivable or at least to leave the
space for hooks so that a post-commit xwiki "reload-from-directory" and a
"post-xwiki-save-commit" are hookable to synchronize with whatever you wish.
Well git would be better (better binary compression) but in either case it would be
either bringing
in a large library or depending on an external (non java) application. I'm not too
interested in any
more .war bloat and I'm pretty sure depending on native code is out of the question.
I wonder if
you don't want, right away, a virtual-file-system so that such as an ftp-mount (for
some spaces?) is doable.
There is no reason why anything which could be mounted could not be used. So nfs, nbd,
samba would
definitely work. I'm not familiar with an ftp mount but if it provides a regular
filesystem, it
should make no difference.