I'm suggesting this because if starting from scratch, anyway work has to be done on the dump format and it would add interoperability with CVS and subversion right away without additional work.
Daniel Florey wrote:
Yes, please!! This is what I had in mind for a longer time, but never managed to start working on it: A WebDAV-client-tool that determines the server capabilities by doing some OPTIONS request and retrieves the content by doing the appropriate WebDAV-requests afterwards. This would have the big advantage that it works with different WebDAV-based repositories and works if different Slide instances use different storage configurations. It might be a bit tricky to retrieve not only the content but also properties, locks, acl and versioning information, but it finally would be the most elegant solution. If we find a good XML representation for content/properties etc. we could use this for data import as well. The xml-format could consist of nested elements representing each resource. This would enable to "dump" the repository located under a given path and import it to a different location. Optional flags could be used to ignore locks/acl/versioning information. Just a dream... or is someone interested in implementing this? As stated before I had this on my personal roadmap for a while but am very busy at the moment and can hardly find the time to do it.
Cheers, Daniel
"Slide Users Mailing List" <[EMAIL PROTECTED]> schrieb am 24.11.04 23:04:34:
It sounds like writing a client tool to migrate content from one Slide server to another one might be a good option. This should be fairly simple to write using the Webdav client library. Another option that I originally had in mind is to simply perform a database dump on the staging server and upload this to production. Of course, this would preserve the entire version history, which we most likely won't care about on our production server, so a separate tool might be more appropriate.
-Mirko
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
