> Ok, sorry, I missed the WebDAV thingy. You are right. BUT WebDAV is very > limited; see transactions and a standard query API. However, this is > another discussion. > > This is exactly the reason why I won't use Slide for Lenya; I can not > use WebDAV because of its limitations and I do not want to rely on the > _propriatry_ Slide API.
I did not want to program to the propriatry Slide API either ;) Anyway, Slide supports both a standard query API as well as transactions. Seach is standard WebDAV and for transactions, events / notifcation we use the extensions MS proposed... Daniel, the inventor of Projector - which is part of Slide - did exactly that: implement some sort of CMS frontend (i.e. workflow, processing, etc.) against WebDAV. I have recently heard rumors he now adapts it to work with SVN which speaks a WebDAV dialect as well. So, this is well possible and seems to work fine... > And I can not believe that WebDAV is the right API to let a CMS app base > upon (because of the limitations). The way to go IMHO is: > > Use JCR API for heavy weight requirements (tx, query) and provide also a > WebDAV API for low level clients to access the same repo. > > To be honest again, my personal wish is that Slide and Rabbit folks > would work more closely together. I feel the potential of > cross-pollination is great. By the way, I was not able to follow the progress of the Rabbit thing, is there already any sort of useable backend? Does it provide transactions now? Would be interesting to know... Is there any special mailing list I could subscribe to? Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
