From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] manual suggestions and upas/fs bug
Date: Tue, 17 Sep 2002 19:05:35 -0400 [thread overview]
Message-ID: <bde60c923553e4ab80380c9fca1b8b85@plan9.bell-labs.com> (raw)
> We have both client and server bugs here.
Thanks for your pointers. The IMAP client code has been
cobbled together by a few people (myself included) who knew
nothing about IMAP before working on it, so it's not surprising
that these inefficiencies exist.
> And *again* the server said there were no messages, thus
>
> -> 9X4 UID FETCH 1:* UID
>
> is completely bogus. That message range is invalid, and the client
> should know that. However, the server should be responding with
> something like
>
> 9X4 BAD Invalid sequence in FETCH
I don't see why it's invalid and not just empty,
but I agree that it is inefficient for the client to
be sending it.
Russ
next reply other threads:[~2002-09-17 23:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 23:05 Russ Cox [this message]
2002-09-18 2:06 ` Lyndon Nerenberg
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=bde60c923553e4ab80380c9fca1b8b85@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).