9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9P writes for directories
Date: Fri, 27 Mar 2009 21:03:35 -0700	[thread overview]
Message-ID: <3154B9F1-3D80-4D78-B0ED-4BFEDD6B0F97@sun.com> (raw)
In-Reply-To: <5d375e920903271836u674ea674x52dbe10e0491a8d8@mail.gmail.com>

On Mar 27, 2009, at 6:36 PM, Uriel wrote:
> Some of us have been thinking about a 'sane' subset of HTTP plus some
> conventions, that could reasonably map to 9p.

Interestingly enough, that's exactly the quest I'm on. I'd appreciate
a chance
of talking to likeminded folks.

> The main issue is the huge amounts of crud in the HTTP spec and how to
> pick the sensible bits

Ever since I've read "JavaSript: the good parts" (and realized along the
way that the good parts were really quire close to Scheme) I tend
to thing that this approach of trying to identify "the good parts" is
the
only thing that can let me keep sanity in the modern world of
rampant web services. The good news (at least so far) seem to
be that there *are* good parts in HTTP.

> and discard the rest while remaining compatible
> with existing implementations; the main convention that needs to be
> added is a way to list directory contents, likely using something not
> too insane, like JSON.

Yeap.

> With some thought and care one could come up with a very simple,
> RESTful, and almost 9p-mappable replacement for the stinking bloated
> WebDAV and SOAP/XML-RPC abominations.


Can't agree more. Another reason to clean up this mess is a potential
to significantly simplify the way a typical web service is written. With
luck, there could be something as simple as lib9p/libixp (or even
execnet) to make writing webserives simple and fun.

  I'd love to exchange ideas on a more appropriate forum (if there's
any).

Thanks,
Roman.



  reply	other threads:[~2009-03-28  4:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-21  7:00 Roman Shaposhnik
2009-03-26 19:31 ` Roman Shaposhnik
2009-03-26 19:35   ` erik quanstrom
2009-03-26 19:50     ` Roman Shaposhnik
2009-03-26 19:56       ` erik quanstrom
2009-03-26 19:44   ` Eric Van Hensbergen
2009-03-26 20:23     ` Roman Shaposhnik
2009-03-26 20:52       ` erik quanstrom
2009-03-26 20:54       ` Eric Van Hensbergen
2009-03-26 22:05         ` Roman Shaposhnik
2009-03-28  1:36           ` Uriel
2009-03-28  4:03             ` Roman Shaposhnik [this message]
2009-04-19 16:43             ` Enrico Weigelt

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=3154B9F1-3D80-4D78-B0ED-4BFEDD6B0F97@sun.com \
    --to=rvs@sun.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).