digitalextremist opened a new issue, #357: URL: https://github.com/apache/couchdb-nano/issues/357
The `v11` change is causing me to rethink separately instantiating `changesReader` instances myself, so that I can have one per `follow` of a particular changes stream. Putting this issue here as a possible point to contribute an alternative behavior for `changesReader` or factory of `changesReader` instances. Would be great to be able to remove my now-outdated fork of `changesReader` by itself, outside `nano` proper! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
