From: Uriel <uriel@berlinblue.org>
To: 9front@googlegroups.com
Subject: Re: todo
Date: Fri, 1 Apr 2011 10:41:20 -0700 [thread overview]
Message-ID: <AANLkTimUNqYDmeikNcPikiiZvOLb4iACtxiDs90NTjkg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1104011551060.4937@sampi>
On Fri, Apr 1, 2011 at 6:54 AM, Julius Schmidt <aiju@phicode.de> wrote:
>> There's another thing: How _hard_ will Tmove break anything? How much
>> trouble will it be to fix everything to fail gracefully, either for any bad
>> message or just for
>> Tmove (whichever is easier)? Granted, "old software" isn't necessarily
>> included in "everything" but how much work will it be to find and look into
>> every server in
>> /sys/src/cmd?
>
> Clients should do it like this:
> - send TMove
> - get RError back if invalid, then do old style copy and delete, or
> move was successful
>
> One possible problem would be servers crashing on invalid messages. That
> would mean they are *really* fucked up and would make it impossible to
> use that method.
> I would not want our code crash remote servers and a special flag on all
> clients to fix that.
> (We simply can't fix all the servers out there).
No, any sane server will simply kick out and disconnect any client
that sends an *invalid* message, Tmove is not part of 9P and is
invalid. 9P is not HTTP or some other asstard protocol that is
supposed to deal with any magic crap you dump on it, and that is one
of the reasons 9P has remained sane and implementing HTTP properly has
become an impossible task.
The "be liberal with what you accept and conservative with what you
send" dogma is the bullshit the web is built on.
uriel
next prev parent reply other threads:[~2011-04-01 17:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <405d44d0ddf24c71ff94c72804f03bec@gmx.de>
2011-03-30 20:57 ` todo Stanley Lieber
2011-03-30 22:39 ` todo cinap_lenrek
2011-03-30 22:46 ` todo Stanley Lieber
2011-03-30 22:04 ` todo uriel
2011-04-01 0:30 ` todo Ethan Grammatikidis
2011-04-01 0:47 ` todo Jacob Todd
2011-04-01 0:59 ` todo Uriel
2011-04-01 1:12 ` todo Ethan Grammatikidis
2011-04-01 4:40 ` todo aiju
2011-04-01 7:04 ` todo Uriel
2011-04-01 7:13 ` todo cinap_lenrek
2011-04-01 9:30 ` todo Uriel
2011-04-01 10:18 ` todo cinap_lenrek
2011-04-01 10:24 ` todo Uriel
2011-04-01 11:38 ` todo cinap_lenrek
2011-04-01 13:36 ` todo Ethan Grammatikidis
2011-04-01 13:54 ` todo Julius Schmidt
2011-04-01 17:41 ` Uriel [this message]
2011-04-01 19:02 ` todo Ethan Grammatikidis
2011-04-02 14:22 ` todo aiju
2011-04-02 14:52 ` todo Ethan Grammatikidis
2011-04-01 17:38 ` todo Uriel
2011-04-01 7:09 ` todo cinap_lenrek
2011-04-01 6:14 ` todo Taru Karttunen
2011-05-02 7:30 TODO Uriel
2011-05-02 13:25 ` TODO Julius Schmidt
2011-05-02 17:03 ` TODO Uriel
2011-05-02 18:24 ` TODO Iruatã Souza
2011-05-02 19:33 ` TODO ron minnich
2011-05-02 13:45 ` TODO Jacob Todd
2018-02-24 19:53 TODO Kurt H Maier
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=AANLkTimUNqYDmeikNcPikiiZvOLb4iACtxiDs90NTjkg@mail.gmail.com \
--to=uriel@berlinblue.org \
--cc=9front@googlegroups.com \
/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).