Follow detects whether an url (or db or uri) ends with /_db_updates and changes
its internals accordingly.
There is no need for extending the API and the change is fully backwards compatibel,
because the can't exist a db called _db_updates.
With one exception: If a user was to route a couchdb database on an endpoint
which is _db_updates it will not work the same anymore :)
Btw: I have moved the logic to support the variants to set the db: url and uri into the follow function to allow setting url property of the feed object, because speaking about db sounds wrong in this context.
Follow detects whether an url (or db or uri) ends with
/_db_updatesand changes its internals accordingly.There is no need for extending the API and the change is fully backwards compatibel, because the can't exist a db called
_db_updates. With one exception: If a user was to route a couchdb database on an endpoint which is_db_updatesit will not work the same anymore :)Btw: I have moved the logic to support the variants to set the
db:urlanduriinto thefollowfunction to allow settingurlproperty of the feed object, because speaking aboutdbsounds wrong in this context.