Er... uh... well... actually there's nothing more than some skeleton code and, AFAIK, just the GET method implemented as an example. Unfortunately both me and Jan disappeared from the list, so the work didn't go any further. But I was re-thinking the whole thing actually, since it might make sense to keep Xincon as it is (well... it works, so it would be just a matter of understanding whether Jan is willing to donate it to Apache or license it so that it can be redistributed with
ok, would be possible - but i have still in mind to make a rewrite.
Definitely. You can count on me for it.
Xindice), while moving the Webdav NG stuff to Slide, since there is an impressive effort going on there.
Why do you want to use slide? For me, slide is a cms; it would be cool if you can store cms data in a xindice store, but i don't think that it is the right way for an administration of xindice via webdav!
I'm not actually talking about administration (I'm perfectly happy with the current tools to administer the DB), I'm talking about user interaction with the store. Slide has a *very* strong WebDAV foundation, including advanced features such as versioning (DeltaV!), locking, DASL and so on. It would be IMHO much more difficult to build all these features from scratch than write a Slide Store. But this is yet to be investigated thouroughly, so I'm open to any suggestion, including:
What do you think about writing a simple jndi api like the jndi resource api from tomcat (org.apache.naming.resources )? With this api we could simply use the tomcat webdav servlet.
Actually, writing a JNDI provider was my first suggestion a long time ago. This would be useful not only for WebDAV but for a whole lot of other environments (can you say J2EE? :-)). So yes, this would be a viable way to go. Too bad ATM I'm so short on time :-(
Ciao,
-- Gianugo Rabellino
