user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/6] ds: object lifetime shortening
Date: Tue, 31 Oct 2023 20:42:49 +0000	[thread overview]
Message-ID: <20231031204255.1837649-1-e@80x24.org> (raw)

1 and 2 do the bulk of the work
3 and 4 are things I noticed when working on 2
5 is a fix while preparing for 6
6 is something I've wanted to do for a long time.

Anyways, the code reductions always make me happy.

Eric Wong (6):
  ds: next_tick: shorten object lifetimes
  ds: do not defer close
  ds: move maxevents further down the stack
  watch: simplify DirIdle object cleanup
  pop3: use SSL_shutdown(3ssl) if appropriate
  ds: make ->close behave like CORE::close

 lib/PublicInbox/CidxComm.pm |   2 +-
 lib/PublicInbox/CidxLogP.pm |   2 +-
 lib/PublicInbox/DS.pm       | 143 ++++++++++++------------------------
 lib/PublicInbox/DSKQXS.pm   |   3 +-
 lib/PublicInbox/DSPoll.pm   |   2 +-
 lib/PublicInbox/Epoll.pm    |   5 +-
 lib/PublicInbox/POP3.pm     |   2 +-
 lib/PublicInbox/Select.pm   |   2 +-
 lib/PublicInbox/Watch.pm    |  11 +--
 t/ds-poll.t                 |  14 ++--
 t/epoll.t                   |   4 +-
 11 files changed, 71 insertions(+), 119 deletions(-)

             reply	other threads:[~2023-10-31 20:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 20:42 Eric Wong [this message]
2023-10-31 20:42 ` [PATCH 1/6] ds: next_tick: shorten object lifetimes Eric Wong
2023-10-31 20:42 ` [PATCH 2/6] ds: do not defer close Eric Wong
2023-10-31 20:42 ` [PATCH 3/6] ds: move maxevents further down the stack Eric Wong
2023-10-31 20:42 ` [PATCH 4/6] watch: simplify DirIdle object cleanup Eric Wong
2023-10-31 20:42 ` [PATCH 5/6] pop3: use SSL_shutdown(3ssl) if appropriate Eric Wong
2023-10-31 20:42 ` [PATCH 6/6] ds: make ->close behave like CORE::close 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=20231031204255.1837649-1-e@80x24.org \
    --to=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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).