Hello, Daniel! > -----Original Message----- > From: Slide Users Mailing List [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 28, 2004 5:36 AM > To: [EMAIL PROTECTED] > Subject: AW: Copy Macro Issue > Importance: Low > > Hi Andrey! > This sounds very interesting as I have planned to consolidate > the client and server api on basis of a new Slide API for > Slide 2.2 or 3.0. Have a look at the Slide 3.0 design > approach in the Wiki.
Thanks, I am well aware of these plans. Everything sounds good and I'm looking forward to see the changes you propose implemented. > If you are already working on separating the webdav logic > from the web context this would be a big step in that > direction! Please let me know more details about your ongoing > work as I will start working on the new API soon. > It will be more or less a simple mapping of WebDAV methods to > Java methods. Actually, I've designed and implemented an "adapter" layer - kind of a relatively simple and uniform interface to the Slide core - that provides our domain classes with all necessary methods. Some of them are almost identical to that of the WebDAV (put, get, copy, move, lock, etc.), others are related to security model (permission check, user-role relationship handling) and configuration (we use Domain.xml to store various parameters for the time being). Some of the WebDAV methods (like binding)) are not implemented because we don't need them at the moment If you are interested in the code, I will gladly send it to you but I should talk to my boss first - unfortunately I can not submit anything without his permission. > Thanks for your work so far! Not at all, Daniel. You, committers, are doing the serious work here. And great job it is, indeed. :-) Yours sincerely, Andrey. > > Von: Andrey Shulinsky [mailto:[EMAIL PROTECTED] > Gesendet: Sa 28.08.2004 03:34 > An: 'Slide Users Mailing List' > Betreff: RE: Copy Macro Issue > > > > Hi, Kiran! > > I suspect that the incorrect behavior of the copy method > might be just one more consequence of the big flaw in Slide's > architecture - some important parts of WebDAV's logic > (including versioning) are implemented in the "wedav" layer > only - see the org.apache.slide.webdav package and its sub > packages. That's why the majority of Slide users are working > with the webdav client and don't use the "core" API directly. > However, we've chosen a different approach and had to rewrite > all required methods from the org.apache.slide.webdav.method > package so they can be used in isolation from the web > context. It's not an easy task (and I'm still not sure if we > did everything correctly! :) ) so you probably should go with > the client and ignore the core until it is rearchitected (in > the 3d version, probably). > Indeed, if you use the COPY method to copy a resource, a > non-versioned copy of the resource is created if auto > versioning is off and creates a versioned copy if auto > versioning is on - but it's VHR is not the same as that of > the original. This behavior is WebDAV-compliant, afaik. > > Yours sincerely, > Andrey. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
