Project

General

Profile

Feature #7990

Consider splitting up updates of many events to stay under the maximum formdata limit?

Added by Roel Standaert 6 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
Start date:
01/19/2021
Due date:
% Done:

0%

Estimated time:

Description

When a large amount of events are in the queue, this may exceed the size of requests that the server may accept, or at least the maximum formdata size.

The client could split up these events to stay under that limit.

There's some stuff to figure out to do that, though:

  • What should the maximum size be? The size of the request is not just the size of the events, there are some other parameters and request headers as well.
  • At which point does the client simply have too many events waiting? I think there should be a limit to this.
#1

Updated by Roel Standaert 6 months ago

  • Status changed from New to Resolved
  • Target version changed from future to 4.6.0

This is on GitHub now (master branch).

Also available in: Atom PDF