From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: commit 3286715e509f8ca70efd674d59f6c58e16fdf95a
Date: Mon, 03 Jan 2011 20:16:45 -0500 [thread overview]
Message-ID: <m339p9qxgq.fsf@jhcloos.com> (raw)
That change does not avoid a doubled call to SELECT when the first
finds newer data than gnus last saw, but instead guarantees a second
SELECT in all cases:
read(0, "40884 SELECT \"news@lists.oasis-open.org\"\r\n", 4096) = 42
read(0, "40885 SELECT \"news@lists.oasis-open.org\"\r\n40886 UID FETCH 1:* FLAGS\r\n", 4096) = 69
read(0, "40932 SELECT \"pwg-announce@pwg.org\"\r\n", 4096) = 37
read(0, "40933 SELECT \"pwg-announce@pwg.org\"\r\n", 4096) = 37
read(0, "40934 UID FETCH 1:* FLAGS\r\n", 4096) = 27
read(0, "40935 SELECT \"python-announce-list@python.org\"\r\n", 4096) = 48
read(0, "40936 SELECT \"python-announce-list@python.org\"\r\n", 4096) = 48
read(0, "40937 UID FETCH 1:* FLAGS\r\n", 4096) = 27
etc.
Also, as of commit 70fb02450c4c5ccd9b the M-g case seems to wobble
between issuing the second SELECT and its UID FETCH in a single write(2)
vs each in its own write(2). I have not detected any difference which
would explain when it is a single write(2) vs two write(2)s....
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next reply other threads:[~2011-01-04 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 1:16 James Cloos [this message]
2011-01-11 19:43 ` Lars Magne Ingebrigtsen
2011-01-11 22:49 ` James Cloos
2011-01-22 19:39 ` Lars Ingebrigtsen
2011-01-22 21:47 ` James Cloos
2011-01-22 21:54 ` Lars Ingebrigtsen
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=m339p9qxgq.fsf@jhcloos.com \
--to=cloos@jhcloos.com \
--cc=ding@gnus.org \
/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).