From: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] manual suggestions and upas/fs bug
Date: Tue, 17 Sep 2002 20:06:41 -0600 [thread overview]
Message-ID: <200209180206.g8I26fl0000579@orthanc.ab.ca> (raw)
In-Reply-To: Your message of "Tue, 17 Sep 2002 19:05:35 EDT." <bde60c923553e4ab80380c9fca1b8b85@plan9.bell-labs.com>
-> 9X4 UID FETCH 1:* UID
>> 9X4 BAD Invalid sequence in FETCH
Russ> I don't see why it's invalid and not just empty,
Because the protocol provides other means for discovering how many
messages are in a folder. The client is responsible for determining the
state of the mailbox. Having done so, it should never be in a position
where it issues a FETCH when there are no messages present. The IMAP4
protocol specification is very picky about syntax. It (and most server
implementations) don't allow for *any* reading-in of semantic (or
syntactic) behaviour. (Another example of this is the illegality of
inserting extra whitespace between protocol elements.)
Some people (usually client authors) complain that this is just
a pain in the rear. Others (usually server authors) think it's
a wonderful way to avoid ambiguous behaviour in the protocol.
(For the record: I'm a server author ;-)
If I ever get my P9 network re-built I plan to fix up the IMAP
code.
--lyndon
next prev parent reply other threads:[~2002-09-18 2:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 23:05 Russ Cox
2002-09-18 2:06 ` Lyndon Nerenberg [this message]
2002-09-18 17:03 ` rob pike, esq.
-- strict thread matches above, loose matches on Subject: below --
2002-09-17 13:28 Russ Cox
2002-09-17 4:58 Russ Cox
2002-09-17 4:34 David Swasey
2002-09-17 20:18 ` Lyndon Nerenberg
2002-09-16 19:29 David Swasey
2002-09-17 1:58 ` Lyndon Nerenberg
2002-09-17 8:47 ` Douglas A. Gwyn
2002-09-17 9:17 ` Lucio De Re
2002-09-18 8:37 ` Douglas A. Gwyn
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=200209180206.g8I26fl0000579@orthanc.ab.ca \
--to=lyndon@orthanc.ab.ca \
--cc=9fans@cse.psu.edu \
/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).