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 11:14:29 -0400	[thread overview]
Message-ID: <3aaafc131003150814k983f8d8k99e90abb16c73f32@mail.gmail.com> (raw)
In-Reply-To: <3e1162e61003150734y7c7482fbsfcdca20069cc4ac2@mail.gmail.com>

On Mon, Mar 15, 2010 at 10:34 AM, David Leimbach <leimy2k@gmail.com> wrote:
> I don't know enough about sam's innards to be able to say whether or not
> this could work, but I do like the idea.

I think it's doable because of the way sam's remote mode works -- it
appears to just use pipes.

Therefore, I thought that maybe a multiplexer could sit between a
single sam and several samterms, organizing the protocol messages from
all the different samterms and presenting something sane to the single
sam -R instance. It would have to be convincing to that individual
sam, appearing to be a single `normal' samterm. I think the fact that
sam uses a database-like protocol would make that possible; all the
results of the multiplexer's merging and so forth would be presented
to the sam -R instance as if they were coming in as protocol messages
from a single samterm.

>
> On Mon, Mar 15, 2010 at 7:05 AM, Jorden Mauro <jrm8005@gmail.com> wrote:
>>
>> 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 15: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 [this message]
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

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=3aaafc131003150814k983f8d8k99e90abb16c73f32@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).