From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Regarding 9p based "protocols" message framing
Date: Wed, 21 Mar 2012 16:32:46 -0400 [thread overview]
Message-ID: <9E8A7665-630F-4829-A6CB-84A0E5BB4344@9srv.net> (raw)
In-Reply-To: <CAG3N4d_Qd-dH4pZWXGdqoNTguSjGge1oLahTwJAk5nVLvzXvjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
> What advantages does it have over TCP?
Significantly simpler implementation.
Lower overhead, giving better speed over local links.
Also, although not an advantage of IL per se, there are a few
advantages to Plan 9 having another protocol in the stack,
especially one which can run 9p. It helps guard against any
accidental network-dependent creep.
> Does it worths the effort of tailoring it back in,
It's not hard to get back in. Erik's 9atom has it. Whether it's
worth it or not is hard to say. I like having it, but NAT boxes
(and occasionally non-NAT routers, although that's more
rare) can cause problems. It is slower over common wide-
area links (lacking TCP's congestion control).
> esp. for a fossil/venti site?
It's mandatory if you want to use kenfs; it's entirely optional
in a fossil/venti (or cwfs or kfs or whatever) environment. It's
sort of depends what you want from the system.
Personally, I'd suggest doing it if you have multiple systems
on the same local net for the pedagogical benefits alone.
Anthony
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 210 bytes --]
next prev parent reply other threads:[~2012-03-21 20:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 11:40 Ciprian Dorin Craciun
2012-03-16 17:04 ` Richard Miller
2012-03-16 17:36 ` Russ Cox
2012-03-16 17:55 ` Ciprian Dorin Craciun
[not found] ` <CADSkJJVcsffzZo6En5A8DTApZULxkqCuzXEgKbFvv8eRjm2DpQ@mail.gmail.c>
2012-03-16 17:49 ` erik quanstrom
2012-03-20 11:42 ` Yaroslav
2012-03-20 12:32 ` Dan Cross
2012-03-20 20:30 ` Ciprian Dorin Craciun
2012-03-21 1:22 ` Dan Cross
[not found] ` <CAEoi9W6t2WRPTYU6+JHfAZoRAe6aWxkuCDkXb1G+VAkZZ1kYug@mail.gmail.c>
2012-03-21 1:52 ` erik quanstrom
[not found] ` <CAEoi9W6z_48wm8Jx__Meodnr50g0Ba00wqyfVrv0SP=Xb5ZHcw@mail.gmail.c>
2012-03-20 15:57 ` erik quanstrom
2012-03-21 20:11 ` Yaroslav
2012-03-21 20:32 ` Anthony Sorace [this message]
2012-03-21 20:37 ` erik quanstrom
[not found] ` <CAG3N4d_Qd-dH4pZWXGdqoNTguSjGge1oLahTwJAk5nVLvzXvjQ@mail.gmail.c>
2012-03-21 20:27 ` erik quanstrom
2012-03-21 20:38 ` Anthony Sorace
2012-03-21 20:53 ` erik quanstrom
2012-03-21 21:24 ` cinap_lenrek
2012-03-21 21:27 ` erik quanstrom
2012-03-21 21:35 ` cinap_lenrek
2012-03-21 21:07 ` cinap_lenrek
2012-03-21 21:22 ` erik quanstrom
2012-03-21 21:16 ` David du Colombier
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=9E8A7665-630F-4829-A6CB-84A0E5BB4344@9srv.net \
--to=a@9srv.net \
--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).