[xwiki-devs] [VOTE] Move filesystem attachment storage into the core.
I would like to move the attachment storage code into the trunk for testing and inclusion in 3.0. I would like to put it in /core/xwiki-store/ which can begin the modularization of the storage engine. The filesystem attachment storage is still a work in progress but the main attachment storage class runs. I have added a new type of lock which automatically breaks deadlock and might solve the problem with deletion sometimes blocking. This code depends on and includes: TransactionRunnable which will allow us to evaluate TR in real life situations. Serialization apis for including a refactoring of the existing XMLWriter. File save/delete TransactionRunnables which serve as primitives for safe file saving and deletion on the filesystem. Lock manager which is still brand new and has to be moved into it's own package yet. An EntityReferenceSerializer for getting file paths from document names. This code provides: FilesystemAttachmentStore which is beta and functional. FilesystemAttachmentVersioningStore which is alpha and "you're on your own". along with compatible FilesystemAttachmentContent and ListAttachmentArchive. Here is my +1 for including this in the core so it can be developed and tested in concert. Caleb
On Jan 28, 2011, at 5:33 PM, Caleb James DeLisle wrote:
I would like to move the attachment storage code into the trunk for testing and inclusion in 3.0. I would like to put it in /core/xwiki-store/ which can begin the modularization of the storage engine.
The filesystem attachment storage is still a work in progress but the main attachment storage class runs. I have added a new type of lock which automatically breaks deadlock and might solve the problem with deletion sometimes blocking.
This code depends on and includes: TransactionRunnable which will allow us to evaluate TR in real life situations. Serialization apis for including a refactoring of the existing XMLWriter. File save/delete TransactionRunnables which serve as primitives for safe file saving and deletion on the filesystem. Lock manager which is still brand new and has to be moved into it's own package yet. An EntityReferenceSerializer for getting file paths from document names.
This code provides: FilesystemAttachmentStore which is beta and functional. FilesystemAttachmentVersioningStore which is alpha and "you're on your own". along with compatible FilesystemAttachmentContent and ListAttachmentArchive.
Here is my +1 for including this in the core so it can be developed and tested in concert.
+1 Thanks -Vincent
+1, I'd like to test it as well. Guillaume On Sat, Jan 29, 2011 at 14:08, Vincent Massol <[email protected]> wrote:
On Jan 28, 2011, at 5:33 PM, Caleb James DeLisle wrote:
I would like to move the attachment storage code into the trunk for testing and inclusion in 3.0. I would like to put it in /core/xwiki-store/ which can begin the modularization of the storage engine.
The filesystem attachment storage is still a work in progress but the main attachment storage class runs. I have added a new type of lock which automatically breaks deadlock and might solve the problem with deletion sometimes blocking.
This code depends on and includes: TransactionRunnable which will allow us to evaluate TR in real life situations. Serialization apis for including a refactoring of the existing XMLWriter. File save/delete TransactionRunnables which serve as primitives for safe file saving and deletion on the filesystem. Lock manager which is still brand new and has to be moved into it's own package yet. An EntityReferenceSerializer for getting file paths from document names.
This code provides: FilesystemAttachmentStore which is beta and functional. FilesystemAttachmentVersioningStore which is alpha and "you're on your own". along with compatible FilesystemAttachmentContent and ListAttachmentArchive.
Here is my +1 for including this in the core so it can be developed and tested in concert.
+1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 01/28/2011 05:33 PM, Caleb James DeLisle wrote:
I would like to move the attachment storage code into the trunk for testing and inclusion in 3.0. I would like to put it in /core/xwiki-store/ which can begin the modularization of the storage engine.
The filesystem attachment storage is still a work in progress but the main attachment storage class runs. I have added a new type of lock which automatically breaks deadlock and might solve the problem with deletion sometimes blocking.
This code depends on and includes: TransactionRunnable which will allow us to evaluate TR in real life situations. Serialization apis for including a refactoring of the existing XMLWriter. File save/delete TransactionRunnables which serve as primitives for safe file saving and deletion on the filesystem. Lock manager which is still brand new and has to be moved into it's own package yet. An EntityReferenceSerializer for getting file paths from document names.
This code provides: FilesystemAttachmentStore which is beta and functional. FilesystemAttachmentVersioningStore which is alpha and "you're on your own". along with compatible FilesystemAttachmentContent and ListAttachmentArchive.
Here is my +1 for including this in the core so it can be developed and tested in concert.
+1 for the idea, I'll look at the code to verify it's OK soon. -- Sergiu Dumitriu http://purl.org/net/sergiu/
+0 Thanks, Marius On 01/28/2011 06:33 PM, Caleb James DeLisle wrote:
I would like to move the attachment storage code into the trunk for testing and inclusion in 3.0. I would like to put it in /core/xwiki-store/ which can begin the modularization of the storage engine.
The filesystem attachment storage is still a work in progress but the main attachment storage class runs. I have added a new type of lock which automatically breaks deadlock and might solve the problem with deletion sometimes blocking.
This code depends on and includes: TransactionRunnable which will allow us to evaluate TR in real life situations. Serialization apis for including a refactoring of the existing XMLWriter. File save/delete TransactionRunnables which serve as primitives for safe file saving and deletion on the filesystem. Lock manager which is still brand new and has to be moved into it's own package yet. An EntityReferenceSerializer for getting file paths from document names.
This code provides: FilesystemAttachmentStore which is beta and functional. FilesystemAttachmentVersioningStore which is alpha and "you're on your own". along with compatible FilesystemAttachmentContent and ListAttachmentArchive.
Here is my +1 for including this in the core so it can be developed and tested in concert.
Caleb
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 On Fri, Jan 28, 2011 at 17:33, Caleb James DeLisle <[email protected]> wrote:
I would like to move the attachment storage code into the trunk for testing and inclusion in 3.0. I would like to put it in /core/xwiki-store/ which can begin the modularization of the storage engine.
The filesystem attachment storage is still a work in progress but the main attachment storage class runs. I have added a new type of lock which automatically breaks deadlock and might solve the problem with deletion sometimes blocking.
This code depends on and includes: TransactionRunnable which will allow us to evaluate TR in real life situations. Serialization apis for including a refactoring of the existing XMLWriter. File save/delete TransactionRunnables which serve as primitives for safe file saving and deletion on the filesystem. Lock manager which is still brand new and has to be moved into it's own package yet. An EntityReferenceSerializer for getting file paths from document names.
This code provides: FilesystemAttachmentStore which is beta and functional. FilesystemAttachmentVersioningStore which is alpha and "you're on your own". along with compatible FilesystemAttachmentContent and ListAttachmentArchive.
Here is my +1 for including this in the core so it can be developed and tested in concert.
Caleb
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
My +1. paul Le 28 janv. 2011 à 17:33, Caleb James DeLisle a écrit :
I would like to move the attachment storage code into the trunk for testing and inclusion in 3.0. I would like to put it in /core/xwiki-store/ which can begin the modularization of the storage engine.
The filesystem attachment storage is still a work in progress but the main attachment storage class runs. I have added a new type of lock which automatically breaks deadlock and might solve the problem with deletion sometimes blocking.
This code depends on and includes: TransactionRunnable which will allow us to evaluate TR in real life situations. Serialization apis for including a refactoring of the existing XMLWriter. File save/delete TransactionRunnables which serve as primitives for safe file saving and deletion on the filesystem. Lock manager which is still brand new and has to be moved into it's own package yet. An EntityReferenceSerializer for getting file paths from document names.
This code provides: FilesystemAttachmentStore which is beta and functional. FilesystemAttachmentVersioningStore which is alpha and "you're on your own". along with compatible FilesystemAttachmentContent and ListAttachmentArchive.
Here is my +1 for including this in the core so it can be developed and tested in concert.
Caleb
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (7)
-
Caleb James DeLisle -
Guillaume Lerouge -
Marius Dumitru Florea -
Paul Libbrecht -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol