Commit 4392b57e authored by Andrew Newdigate's avatar Andrew Newdigate 💬

Add more documentation around how polling works

parent cb64d81b
Pipeline #50373732 (#691762) failed with stages
in 69 minutes and 36 seconds
# Polling with ETag caching
TODO: we should probably document the side-effect that sharing etags per path, not on the full URL means that invalidating the path will intentionally invalidate all query strings for that path.
TODO: Yes, and we should also note that the content itself will still be different - we only use the path for computing the ETag, not for the body (when there is a cache miss).
Polling for changes (repeatedly asking server if there are any new changes)
introduces high load on a GitLab instance, because it usually requires
executing at least a few SQL queries. This makes scaling large GitLab
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment