9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Thrift RPC
Date: Mon, 17 Aug 2009 08:27:06 -0700	[thread overview]
Message-ID: <3e1162e60908170827k28ed8aqfeddcdf9759ebfca@mail.gmail.com> (raw)
In-Reply-To: <5d375e920908132041r5f6d2662o869b96883f30ba18@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]

On Thu, Aug 13, 2009 at 8:41 PM, Uriel <uriel99@gmail.com> wrote:

> On Thu, Aug 13, 2009 at 4:27 PM, David Leimbach<leimy2k@gmail.com> wrote:
> > On 8/13/09, erik quanstrom <quanstro@coraid.com> wrote:
> >>> we don't use te*xt for 9p, do we?
> >>
> >> the difference being, 9p is the transport not
> >> the representation of the data and 9p has
> >> a fixed set of messages.
> >>
> >
> > Also 9p aims at file systems pretty obviously where Thirft is a
> > generic RPC mechanism with stub compilers for bindings for several
> > languages.
> >
> > I have not been able to convince coworkers that filesystem namespaces
> > are the way to go.  I think they think it is too hard.
> >
> > *shrug*  you can lead a horse...
>
> Funny, the problem I usually have is that people think file systems
> are *too simple*, oh, no data types other than *byte stream* and
> *drectory*, and no type checking! We are all going to die!
>

Interestingly enough, people dealing with management of servers have been
using stuff like SMASH CLP, which uses commands like "cd" and "show", which
may as well have been "cd" or "ls" to access system resources.

I'm talking about smart power strips from Raritan, which have power
monitoring and control per receptacle.

So really, a lot of the things I do like about plan 9 are just nearly there
in the wild in some cases, and feel quite natural.

The next step is to make a generic CLP filesystem that speaks 9p :-).  Might
be fun, but I don't have an extra 600 dollars for a power strip right now
:-)


>
> People seem to have trouble believing something simple can do a job
> that they have convinced themselves needs to be very complicated.
>

Seems like in some cases people still do want the simplicity of filesystem
access.  So perhaps we're not entirely screwed yet.  :-)

Dave


>
> uriel
>
>

[-- Attachment #2: Type: text/html, Size: 2897 bytes --]

  parent reply	other threads:[~2009-08-17 15:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13  3:33 Roman Shaposhnik
2009-08-13  3:49 ` Tim Newsham
2009-08-13  4:33   ` Roman Shaposhnik
2009-08-13  3:56 ` erik quanstrom
2009-08-13  6:49   ` Daniel Lyons
2009-08-13 10:01     ` Uriel
2009-08-14  4:58       ` Nate S
2009-08-13  8:33   ` Richard Miller
2009-08-13  8:42 ` roger peppe
2009-08-13 13:43   ` erik quanstrom
2009-08-13 14:27     ` David Leimbach
2009-08-13 15:06       ` roger peppe
2009-08-14  3:41       ` Uriel
2009-08-14 13:19         ` matt
2009-08-17 15:27         ` David Leimbach [this message]
2009-08-17 15:44           ` ron minnich
2009-08-17 15:58             ` David Leimbach
2009-08-14 19:08   ` Roman V. Shaposhnik

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=3e1162e60908170827k28ed8aqfeddcdf9759ebfca@mail.gmail.com \
    --to=leimy2k@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).