|Stable release||5.2a / June 4, 2011|
Code Co-op is a distributed revision control system of the replicated type.
It uses peer-to-peer architecture to share projects among developers and to control changes to files. Instead of using a centralized database (the repository), it replicates its own database on each computer involved in the project.
The replicas are synchronized by the exchange of (differential) scripts. The exchange of scripts may proceed using different transports, including e-mail (support for SMTP and POP3, integration with MAPI clients, Gmail) and LAN.
Code Co-op has a built-in peer-to-peer wiki system, which can be used to integrate documentation with a software project. It is also possible to create text-based Wiki databases, which can be queried using simplified SQL directly from wiki pages.
- Distributed development support through E-mail, LAN, or VPN
- Change-based model—modifications to multiple files are checked in as one transaction
- File additions, deletions, renames, and moves are treated on the same level as edits—they can be added in any combination to a check-in changeset
- File changes can be reviewed before a check-in using a built-in or user-defined differ
- Synchronization changes can be reviewed in the same manner by the recipients
- Three-way visual merge
- Project history is replicated on each machine. Historical version can be reviewed, compared, or restored
- Integration with Microsoft SCC clients, including Visual Studio
The development of Code Co-op started in 1996, when Reliable Software, the distributed software company that makes it, was established. Reliable Software needed a collaboration tool that would work between the United States and Poland. The only dependable and affordable means of communication between the two countries was e-mail, hence the idea of using e-mail for the exchange of diffs. Of course, with such slow transport, using a centralized repository was unfeasible. Each user of Code Co-op had to have a full replica of the repository, including the history of changes.
The problem was reduced to that of designing a distributed database that uses slow and unreliable transport for synchronization (later, faster LAN transport was also added). It also followed that the synchronization between multiple sites must use some kind of peer-to-peer protocol.
Code Co-op is an example of a distributed database. Local repositories are considered the replicas of this virtual database. Each check-in corresponds to a distributed commit—a non-blocking version of a two-phase commit.