Hello, I am not sure to understand what really is the difference between spi2dav and spi2davex...
How can we take advantages of the batch operation of spi2davex in a single thread client process that read/writes on the repository? For writing, maybe it could hold changes and make a single update request for them all later... (at session.save() ?) For reading, maybe getNodes() and getProperties() returns all nodes and all properties and getNode(), getProperty() only one result at a time... Any details? I can't find a page explaining the differences. F Le 2010-01-12 à 3:20 AM, Alexander Klimetschek a écrit : > On Wed, Jan 6, 2010 at 01:47, ChadDavis <[email protected]> wrote: >> I see two things in the jackrabbit-spi2dav component. I'm on 2.0. >> What is the difference between these? > > They use different granularities of WebDAV to implement the JCR (or > better SPI operations). spi2dav uses single GET/PUT/etc. requests for > each property, which is following the WebDAV spec, but can be a bit > slow. davex uses batch operations that can read or write multiple > resources (= nodes and properties) at once. > > Regards, > Alex > > -- > Alexander Klimetschek > [email protected]
