Use a queue for all requests in the request manager

[provokateurin]

[Leptopoda]

The queue can hold a record with a priority and a request.
This way we can ensure critical requests like the startup checks from the framework happen earlier.
Once images also use the request manager they can get a lower one.

I propose 4 levels:

• critical (should only be used for the startup checks inside the frsmework)
• high
• normal
• low (secondary content like image previews)

[provokateurin]

Another thing we could add is that requests with the same key are deduplicated. If there is already a request in the queue with the same "target" then the second request can just listen to the result of the first one.

[Leptopoda]

Another thing we could add is that requests with the same key are deduplicated. If there is already a request in the queue with the same "target" then the second request can just listen to the result of the first one.

Great Idea.

I don't like adding all of this functionality to the RequestManager directly.
Keeping #800 in mind we should add a separate RequestBloc that handles the queue and priorities and can handle the global error and loading states.
The RequestBloc can then invoke the current RequestManager to do the actual request.

[provokateurin]

For the initial thing it would like to just have a simple queue without anything fancy to avoid all the lag that happens when everything is trying to load at once.

[Leptopoda]

I think that just a simple queue will not work.
If the connection to the server takes a while (slow server, bad connectivity) the queue will also slow down fetching the data from the cache.

Ideally the cache should not be affected and only the real network request should be queued.

[provokateurin]

Yep, though that should still be achievable using a simple queue?

[Leptopoda]

I haven't looked into it but from the description the pool package looks good.
Sounds like it would also handle timeouts.

[provokateurin]

Ideally it needs to also handle priorities 🤔