Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update all categories at once #31

Open
eddydc opened this issue Apr 12, 2021 · 1 comment
Open

Update all categories at once #31

eddydc opened this issue Apr 12, 2021 · 1 comment

Comments

@eddydc
Copy link

eddydc commented Apr 12, 2021

Not really an issue but an annoyance bothering me for a long while. I would like to update all pois for all categories at once instead off doing this per category separately. I've a large number of pois and categories.
Can this option be provided pls?

@Lee-Carre
Copy link

update all pois for all categories at once

I suggest this not be literal and, instead, put all requests into a queue which is handled M at a time (M=2 might be a sensible default).

Especially for the case of different datasets using the same hostname, do not open more than 2 (as per the HTTP spec) concurrent connections to the same host. While fetching, don't have more than S outstanding / ongoing requests to any individual host (S=2 as default?). Though, I doubt that PinPoi uses HTTP pipeline-ing.

Some of the data sources I use, dynamically-generate the response, so I would like (read: need) the following:

  • retention of manually updating each Collection, individually
  • being able to limit requests to 1 at a time, for that host
  • there being a sleep / cool down period, between the last query and the next, to that host

Additionally to being able to update

  • individual collections
  • everything / all collections

Being able to

  • update per-category (all collections within that category, but nothing else)
  • regularly update on a schedule (optionally only when connected via unmetered 802.11); this seems better handled in a separate ticket, which I'll open, but thought it worth noting for informing implementation design

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants