TWiki, written in perl, makes extensive use of versioning/diff functionality you mention through the use of RCS, which, IIRC, is the basis for CVS. This method eliminates the need for the repository as such, and merely requires the presence of the RCS files (and RCS).
Unless you _want_ to host your data on a separate machine than the one hosting the wiki, you might consider RCS as an alternative to CVS. OTOH, it is clearly a good idea to base your software on such a tool, given that TWiki does it and has proven to be quite successful. =) Rick piotr malin'ski wrote: > I'm planning to wite a fully featured wiki in Python in one of > frameworks. I've seen some notes about wiki/documentation management > scripts that use SVN as a data storage/versioning. > I've been using SVN a bit but I don't know if it's a good idea to use > it in a wiki engine. Pro: versioning / diffs, Cons: you need your own > svn/cvs repository, can pyLucene or Xapwrap index this? -- http://mail.python.org/mailman/listinfo/python-list
