From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <47b993ff99a5a791dffd072dbe8e7190@9netics.com>
References: <3aaafc131003150705t5832e72fv6b17c1bf6da000ef@mail.gmail.com>
	<47b993ff99a5a791dffd072dbe8e7190@9netics.com>
Date: Mon, 15 Mar 2010 19:14:02 -0400
Message-ID: <3aaafc131003151614y79d903adj25ab96b7f432a766@mail.gmail.com>
From: Jorden Mauro <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [9fans] Collaborative Sam?
Topicbox-Message-UUID: e98498ca-ead5-11e9-9d60-3106f5b1d025

On Mon, Mar 15, 2010 at 6:23 PM, Skip Tavakkolian <9nut@9netics.com> wrote:
> if you carry the idea through, i think you'll reinvent
> 9p and mount :)

Of course, the idea could be done as a 9p file server. However, I
think the fact that sam already uses a protocol with database-like
semantics would greatly reduce the work needed. I also don't think
that such a scheme would allow for real-time update in samterm (though
of course, I don't know if my original idea would, either!)

>
>> How hard would it be to stick a program between a single sam -R and
>> several samterms? I imagine such a program would have to interpret the
>> sam protocol and handle merges and simultaneous updates, but since sam
>> essentially treats files operations as database transactions, it seems
>> like sam's protocol could be very helpful. The possibilities for what
>> such an intermediary program could do are probably limitless, but I
>> was thinking it could make collaborative editing via sam a
>> possibility.
>>
>> I don't know enough about sam's protocol to know if such an idea would work.
>
>
>