Does CouchDB need a server‑side abort mechanism for cancelled _changes feeds and view queries?
The goal is to ensure that when a client cancels a request—by closing the TCP connection or exceeding a timeout—any server‑side work such as ongoing map‑reduce index updates or _changes feed processing is halted promptly to avoid wasting CPU and I/O resources. CouchDB currently stops transmitting _changes events after detecting a closed socket, but ongoing v
couchdb