The constant polling of the debugtoolbar has made debugging certain things difficult.
I tried turning off logging, but that was too strict a measure.
I'd like to suggest a configurable polling option.
Looking at the code, toolbar.dbtmako just uses a javascript EventSource to handle the ajax data
source = new EventSource('/_debug_toolbar/sse?request_id=${request_id}');
looking at views.py , it's seems that we're not really using a server-side push, but falling back on the HTML spec that will have browsers repoll/reconnect/retry in 3second intervals
The constant polling of the debugtoolbar has made debugging certain things difficult.
I tried turning off logging, but that was too strict a measure.
I'd like to suggest a configurable polling option.
Looking at the code,
toolbar.dbtmako
just uses a javascript EventSource to handle the ajax datalooking at
views.py
, it's seems that we're not really using a server-side push, but falling back on the HTML spec that will have browsers repoll/reconnect/retry in 3second intervalsThe current template for the payload is:
And we can minimally edit that to have full control of the retry (in ms)
The default behavior is equivalent to 3000 ; a simple config file edit could let this be 60,000 or 1,000 or whatever is easiest for a developer.