unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: Cheap way to check for new messages in a thread
Date: Mon, 27 Mar 2023 19:10:49 +0000	[thread overview]
Message-ID: <20230327191049.M277377@dcvr> (raw)
In-Reply-To: <aaniyhk7wfm4e6m5mbukcrhevzoc6ftctyrfwvmz4fkykwwtlj@mverfng6ytas>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Hello:
> 
> For the bugzilla integration work I'm doing, I need a way to check if there
> were any updates to a thread since the last check. Right now, I'm just
> grabbing the full thread, parsing it and seeing if there are any new
> message-IDs that we don't know about, but it's very wasteful. Any way to just
> issue something like "how many messages are in a thread with this message-id"
> or "are there any updates to a thread with this message-id since
> YYYYMMDDHHMMSS?

  lei q -t --only /path/to/(inbox|extindex) mid:$MSGID rt:APPROXIDATE..

Returns JSON and won't retrieve message bodies from git.

I wouldn't query down to the second due to propagation delays,
clock skew, etc, though.


There might be a JMAP endpoint I can implement for WWW which
only retrieves that info, but getting backreferences (required
by the JMAP spec) to work properly seemed painful.

  reply	other threads:[~2023-03-27 19:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 15:08 Cheap way to check for new messages in a thread Konstantin Ryabitsev
2023-03-27 19:10 ` Eric Wong [this message]
2023-03-27 20:47   ` Konstantin Ryabitsev
2023-03-27 21:38     ` Eric Wong
2023-03-28 14:04       ` Konstantin Ryabitsev
2023-03-28 19:45         ` Eric Wong
2023-03-28 20:00           ` Konstantin Ryabitsev
2023-03-28 22:08             ` Eric Wong
2023-03-28 23:30               ` Konstantin Ryabitsev
2023-03-29 21:25                 ` Eric Wong
2023-03-30 11:29                   ` Eric Wong
2023-03-30 16:45                     ` Konstantin Ryabitsev
2023-03-31  1:40                       ` Eric Wong
2023-04-11 11:27                         ` Eric Wong
2023-06-16 19:11                     ` Konstantin Ryabitsev
2023-06-16 23:13                       ` [PATCH] www: use correct threadid for per-thread search Eric Wong
2023-06-21 17:11                         ` Konstantin Ryabitsev

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=20230327191049.M277377@dcvr \
    --to=e@80x24.org \
    --cc=konstantin@linuxfoundation.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).