On Wed, Aug 13, 2008 at 11:39 PM, Avi Bryant <avi at dabbledb.com> wrote:

>> Ok, that makes sense for a company. What about projects like Seaside
>> or OB where there are numerous developers that frequently change?
>
> Managing the client side of that is easy: the image needs to know to
> look for new .mcr files in a certain directory and add them
> automatically as read-only repositories.  The rsync script needs to
> look for these on the server and download them automatically.

To reactivate an old thread - getdropbox.com, which just came out of
private beta, strikes me as perfect for this kind of shared, synced
directory.  We're also considering using it for MC1 repositories, but
it would be much more storage and bandwidth efficient to use it with
MC2.

Avi