9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Adriano Verardo <adriano.verardo@mail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] About IL
Date: Tue, 20 Oct 2015 19:53:42 +0200	[thread overview]
Message-ID: <56267FA6.9000502@mail.com> (raw)
In-Reply-To: <CAOw7k5jSixsHX7bdR76JoeFhm4StDFQy-tZDMcWjAxKJTeetzA@mail.gmail.com>

Charles Forsyth wrote:
>
> On 20 October 2015 at 17:14, Adriano Verardo <adriano.verardo@mail.com
> <mailto:adriano.verardo@mail.com>> wrote:
>
>     Could IL be actually more effective than TCP/IP in a closed net ?
>     I think about a robotic application using very small cpus.
>     What about Styx -- ore something similar - over IL ?
>
>
> Styx is (now) the same as 9P, and it was always similar: not a
> transport protocol, but a service protocol that ran on any suitable
> transport,
> and not just on IP networks.
Ok
> We used a special link-level transport protocol over infra-red to use
> Styx to talk to a programmable Lego brick from Inferno. It did
> run-length encoding, and possibly some other compression scheme.
Possible scenarios:
1) distributed intelligence to control complex mechanic devices. Say
arms but in general whatever else.
2) coordination of 2+ submarine robots. Thus a very very low bandwidth
(kHz).
3) coordination of flying drones.
>
> All you need is a transport protocol that reliably preserves content
> and order. It doesn't need to keep record boundaries,
> although transport protocols are sometimes simpler if you do, working
> with messages instead of a raw byte stream.
> It doesn't need to be an Internet Protocol (ie, there doesn't need to
> be an IP layer).
Yes, I have a little experience with 9P. In a industrial appl I did
years ago, Plan9 nodes export drivers etc as a "control/monitor" file
server.
The Plan9 subsystem is monitored (also) through a Windows/P9 interface.
Mission critical and a little complex but no bandwidth
constraints.
> 9P itself will multiplex many clients
> on the same connection to a server, so you don't need a higher-level
> multiplexing protocol using ports etc.
> In fact, using attach names, you can have several different server
> trees served on the same connection to many different clients.
So, is it correct to say that IL is a too complex solution although
lighter than TCP/IP ?

adriano




  reply	other threads:[~2015-10-20 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 16:14 Adriano Verardo
2015-10-20 17:16 ` Charles Forsyth
2015-10-20 17:53   ` Adriano Verardo [this message]
2015-10-20 18:14     ` Skip Tavakkolian

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=56267FA6.9000502@mail.com \
    --to=adriano.verardo@mail.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).