public inbox for pdm-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Datacenter Manager development discussion
	<pdm-devel@lists.proxmox.com>,
	Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pdm-devel] [PATCH datacenter-manager] ui: resource tree: use AsyncPool to cancel obsolete pending loads
Date: Thu, 17 Apr 2025 17:43:34 +0200	[thread overview]
Message-ID: <bf7a59ee-077d-4d64-9536-e03263345985@proxmox.com> (raw)
In-Reply-To: <20250416113232.2488103-1-d.csapak@proxmox.com>

Am 16.04.25 um 13:32 schrieb Dominik Csapak:
> Currently, if a new serach term is given, a new load will occur if the
> INPUT_BUFFER_MS time is reached. Any old in-flight API requests are not
> canceled, and might still arrive.
> 
> To prevent that, use an AsyncPool and refresh that when the search term
> changes.

I forgot a few details here, but would it be possible to provide a wrapper
component for such things? I.e. fields where editing will trigger an API
request. As to me, it feels like this is an easy error to make for any
such fields, especially as it normally won't be noticed if tested locally
with <1ms network latency and the often relatively smaller (test) setups,
where the code querying the data in the backend needs only a few ms too.

But in any way not something that needs to delay applying this patch.



_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel


  reply	other threads:[~2025-04-17 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 11:32 Dominik Csapak
2025-04-17 15:43 ` Thomas Lamprecht [this message]
2025-04-18  6:10   ` Dominik Csapak
2025-04-18  7:29     ` Dominik Csapak
2025-04-18  7:47 ` Dominik Csapak

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=bf7a59ee-077d-4d64-9536-e03263345985@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=pdm-devel@lists.proxmox.com \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal