i think that if we extend the datastore interface, especially the function : DataRecord<http://jackrabbit.apache.org/api/1.6/org/apache/jackrabbit/core/data/DataRecord.html> *addRecord<http://jackrabbit.apache.org/api/1.6/org/apache/jackrabbit/core/data/DataStore.html#addRecord%28java.io.InputStream%29> *(InputStream<http://java.sun.com/j2se/1.4.2/docs/api/java/io/InputStream.html?is-external=true> stream) To add more information, for example: workspace name, node name, property name ... it would be possible to create more complex implementation.
2010/1/25 Thomas Müller <[email protected]> > Hi, > > Currently there is only data store per repository. If you need a data > store per workspace, then you need one repository per workspace. > > > - Assign a datastore per workspace (customer) so it's possible to measure > > (and limit) storage usage for a given customer > > This more sounds like an "accounting problem" than a "technical > problem". Could you add some accounting code to the application? For > example, use an ObservationListener to calculate the disk space used > by a user (workspace). Or, use a wrapper around the input stream and > measure / limit storage like this. > i will try observationListener, sounds interesting > > > - Dynamic allocation, so newer or more accessed nodes will be stored on > > faster disk and old nodes will be mover to sata slower disk > > Such a 'caching data store' would be nice. It's a bit tricky to > implement I think. Currently, there is no such implementation, however > patches are always welcome. > I'm about to start working in this implementation, i will open a new thread in the list as soon as i have some interesting result. > > Regards, > Thomas > -- Jose Hernandez 675599600 Isthari http://www.isthari.com
