#30722: Rate-limit autocomplete widgets Ajax requests
-------------------------------------+-------------------------------------
Reporter: Federico Jaramillo | Owner: Federico
Martínez | Jaramillo Martínez
Type: | Status: assigned
Cleanup/optimization |
Component: contrib.admin | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Federico Jaramillo Martínez):
* needs_better_patch: 1 => 0
Comment:
Updated the patch, tests are passing.
500 was the number that gave me the least amount of unnecessary requests
while still giving a perception of responsiveness, but those were more or
less empiric tests with some co-workers. More than 500 **felt** slow.
We found that less than 250 would start sending requests for slow typers.
Given that this would be a default, I proposed 500 as that was the higher
acceptable number for us. If a specific site requires a lower delay, it
can be overridden on a custom widget or by overriding
`resources/static/admin/js/autocomplete.js`.
I thought that it would be more important to avoid unnecessary requests
over the gain of 100ms in the admin area.
--
Ticket URL: <https://code.djangoproject.com/ticket/30722#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.be6d2eeb774e5a4bd0e95fd8f61957a7%40djangoproject.com.
