9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jorden Mauro <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Collaborative Sam?
Date: Mon, 15 Mar 2010 19:14:02 -0400	[thread overview]
Message-ID: <3aaafc131003151614y79d903adj25ab96b7f432a766@mail.gmail.com> (raw)
In-Reply-To: <47b993ff99a5a791dffd072dbe8e7190@9netics.com>

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.
>
>
>



      reply	other threads:[~2010-03-15 23:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 14:05 Jorden Mauro
2010-03-15 14:34 ` David Leimbach
2010-03-15 15:14   ` Jorden Mauro
2010-03-15 15:30     ` David Leimbach
2010-03-15 17:04       ` Chad Brown
2010-03-15 17:38         ` Jorden Mauro
2010-03-15 17:47       ` Jorden Mauro
2010-03-15 22:23 ` Skip Tavakkolian
2010-03-15 23:14   ` Jorden Mauro [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3aaafc131003151614y79d903adj25ab96b7f432a766@mail.gmail.com \
    --to=jrm8005@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).