Am Sam, 2002-03-16 um 19.01 schrieb Gianugo Rabellino: > What do you mean exactly with "communicate with other apis"? it should work with the XML:DB api and the internal api. > > But there are problems with both impl: > > if you change something not through the webdav interface (for example > > del a resource with the xmldb api) you will get ghosts in slide > > I don't really understand the reason for this (note, I don't know Slide > that much). Care to share some words on this topic? ok, sorry i mixed up the tamino slide store with the slide funktionality. This problem could be solved, but i think it is the wrong way. Slide is designed as a complete content management system and not as a webdav frontend. It has something linke a virtual filesystem (with security, properties ...) where you can mount your databases! And it is very cool!
> I had a (unfortunately quick) look at your code and I undertand > perfectly what you are saying. :-) Basically I was following the same > approach but I was scared by a class that could well end up to thousands > of lines (yours is 1326...) so I was designing it as a set of classes > (one per method) and a servlet frontend. yes i had this in mind. i started to extend on the tomcat webdav impl, but there was no chance. (1326 are terrible!!!!!!! When i first opened the tomcat webdav servlet i was shocked: 3061 lines!) > Also, I was planning to use > XSLT for XML responses, which seems to me the most flexible way (also this is cool, i thought about it, before i started developing xincon, but what is with the performace? i tried XSLT for highlighting the xml sources in xincon. Now i use a modified dom4j xmlwriter. > would take the catalina dependency out). it is only one class from catalina. > Finally, log4j... well, AFAIK > there is a general consensus on using Avalon, so I'd suggest to use LogKit. ok > In short: I'd like to work on this with you (given also that I see you > are planning a rewrite). What about it? let's do it! you will hear from me! ciao Jan
