From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [RFC] pop3: support `?limit=$NUM' parameter in mailbox name
Date: Tue, 19 Sep 2023 17:28:09 -0400 [thread overview]
Message-ID: <20230919-buggy-unsent-411b34@meerkat> (raw)
In-Reply-To: <20230918211422.M309741@dcvr>
On Mon, Sep 18, 2023 at 09:14:22PM +0000, Eric Wong wrote:
> > Oh, I did notice what is probably unintentional behaviour -- passing
> > ?limit=XXX affects all mailbox access, not just the initial retrieval.
> >
> > E.g. if I configured pop3 with ?limit=128, then leave for the weekend and
> > return on Monday, I will only be able to retrieve 128 new messages, regardless
> > of how many arrived over the weekend.
> >
> > I'm not sure if this is what was intended -- I think it makes more sense to
> > have ?limit=XXX only affect the initial retrieval. In all other cases, when a
> > tracking uuid cookie is present, it should return all messages regardless of
> > ?limit=.
> >
> > Does that make sense?
>
> I think there should be an initial_limit parameter in addition to the
> current limit. initial_limit would be more suited for cronjobs and
> such running on 24/7 systems. The regular limit would be better
> for systems with intermittent access and could go weeks w/o being
> online (including situations where somebody restored a system from
> a months/years-old backup).
I'm game with that. Maybe even shorten that to l= and il=? I'm still worried
about the field size limit a bit.
> Not feeling well, will try to work on it once (or if) I feel better.
Please take care!
-K
next prev parent reply other threads:[~2023-09-19 21:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 21:08 pop3 usability thoughts Konstantin Ryabitsev
2023-09-12 22:40 ` [RFC] pop3: support `?limit=$NUM' parameter in mailbox name Eric Wong
2023-09-13 6:20 ` Eric Wong
2023-09-13 15:33 ` Konstantin Ryabitsev
2023-09-13 22:03 ` Eric Wong
2023-09-15 19:17 ` Konstantin Ryabitsev
2023-09-13 16:08 ` Konstantin Ryabitsev
2023-09-14 0:38 ` Eric Wong
2023-09-15 20:03 ` Konstantin Ryabitsev
2023-09-15 20:41 ` Eric Wong
2023-09-18 13:46 ` Konstantin Ryabitsev
2023-09-18 21:14 ` Eric Wong
2023-09-19 21:28 ` Konstantin Ryabitsev [this message]
2023-09-22 2:18 ` [PATCH] pop3: support initial_limit " Eric Wong
2023-09-22 18:02 ` Konstantin Ryabitsev
2023-09-22 18:38 ` Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230919-buggy-unsent-411b34@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).