[pmwiki-devel] SCS Backend?

[Stirling Westrup]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yesterday a friend was asking me how hard it would be to use a distributed
source control system like monotone or mercurial as a storage backend to PmWiki.

We've been talking about doing some collaborative work and tracking it via
PmWiki. The thing is, he would like to have an automatically-updated copy of
the wiki that he can work with when offline.

Now I know that there have been several other backend storage projects for
PmWiki, so I told him that I thought it was possible. The thing is, I have no
idea how much work is involved, or even exactly what one would need to change.

My first impression is that one merely has to replace the pagestore class with
another one, but I doubt that its that simple. One problem I can imagine, for
instance, is that we might want to use the SCS's diff algorithm rather than
the default PmWiki one when generating a history. That history may not end up
saved inside the individual files as a result. I'm not really sure what
ramification that may have.

So, I'm interested in the experiences of folks who have done this sort of
operation on PmWiki before, how hard it was, and what gotchas they encountered.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGYBdC5dZZEoPlyIURArYwAJwNbYYPn9n+8RXPP7hQhlruAJzj0QCgrFf4
T2y31yesbDiLB4d3bzsZNzE=
=yuK7
-----END PGP SIGNATURE-----