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: Thu, 26 Mar 2009 12:50:47 -0700 [thread overview]
Message-ID: <0A1D14F2-63A1-432C-9B35-E1C6A4276DE4@sun.com> (raw)
In-Reply-To: <5bfa6a719e49e0e7c84a73d1257a8a66@quanstro.net>
On Mar 26, 2009, at 12:35 PM, erik quanstrom wrote:
>> question: is there anything that HTTP makes us lose except
>> for the transactional nature of create?
>
> sanity?
That's dead and buried already :-( But I've got be honest
with you -- REST is actually the closes thing to 9P
that has a potential to excite PHBs and thus get approved.
HTTP is stateless, yes, but the biggest PITA that brought us
so far would be authentication, not the core functionality.
>> to "create" would be POST with a metadata payload on a
>> "subdirectory" URI. But of course, it is not a create at all.
>
> i'm not sure what fine hair you're trying to split. why can't the
> post contain the same information a create would?
If "hair splitting" is the answer to the original question -- that's
completely fine. In fact, I was looking for that to be an answer.
It's just that everytime I see something being explicitly forbidden
in 9P spec there's usually a pretty good reason for that.
Thanks,
Roman.
next prev parent reply other threads:[~2009-03-26 19:50 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 [this message]
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
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=0A1D14F2-63A1-432C-9B35-E1C6A4276DE4@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).