Re: [xwiki-devs] XML Encoding for Application Development

What about having a "virtual" subversion checkin URL associated with any Xwiki site. There's be a restricted set of files that could be checked in, where most Xwiki documents are ".vm" files -- velocity macro. The subversion protocol, which is just HTTP, would actually be implemented in Xwiki, such that subversion checkins would checkin a new version (doing all the xml-encoding and name-fixing needed for storage in xwiki's db). A subversion checkout would de-encode the XML and reverse-name-fix for 1-1 correspondence with the checked-in file. Fancier subversion protocol functionalit like diffs and retrieving revs, etc could all be "not implemented" but the basics of checkin/checkout to the "head" would still work. Most of subversion's "RCS" facilities are already implemented in Xwiki's document store, so this proposed feature would represent a bridge between subversion and the document store. The user would end up using whatever preferred GUI frontend (or commandline) svn tools available.... There'd be numerous limitations on this virtual subversion store that would just cause it to "error out" if inappropriate filenames or directories are attempted checkin (e.g. "." in the name). Errors would also occur w/ invalid xwiki db read/write perms for the checkin user. Further, the special subversion repo would also only implement one level of "directory" (representing xwiki spaces) and would require that any non-vm files (aka attachments) have a valid path representing the document name (minus vm exptension). e.g. /<space>/<document>/<attachment>.<ext> for all /<space>/<document>.vm Niels http://nielsmayer.com On Sat, Dec 26, 2009 at 4:16 PM, Andreas Schaefer &lt;schaefera(a)me.com&gt; wrote: