From: Uriel <uriel99@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Thrift RPC
Date: Fri, 14 Aug 2009 05:41:52 +0200 [thread overview]
Message-ID: <5d375e920908132041r5f6d2662o869b96883f30ba18@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60908130727h53b56764v7effe03b711140ae@mail.gmail.com>
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!
People seem to have trouble believing something simple can do a job
that they have convinced themselves needs to be very complicated.
uriel
next prev parent reply other threads:[~2009-08-14 3:41 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 [this message]
2009-08-14 13:19 ` matt
2009-08-17 15:27 ` David Leimbach
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=5d375e920908132041r5f6d2662o869b96883f30ba18@mail.gmail.com \
--to=uriel99@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).