- using the SPI interface, which is kind of a "batch-optimized" and smaller API compared to JCR, but provides the same feature set
just for clarification: the SPI is an internal layer and not meant to be used *instead* of the JCR API. if you are looking for JCR in a remoted environment and decide to take advantage of the SPI you are still encouraged to use the JCR API. the difference is that you will then use the jackrabbit-jcr2spi JCR implementation instead of jackrabbit-core. nevertheless: i will put an extended version of the spi2dav into the sandbox as soon as i get along ((actually i promised to have that done in january)). it uses json blocks for batch-read and batch write... anyway... i will write some lines when i'm done... angela
