anuragvohraec commented on issue #3308: URL: https://github.com/apache/couchdb/issues/3308#issuecomment-860760397
>we have an API to return a sequence in the document I wanted to see if it would make sense having the same kind of API rather than invent something completely new, like returning data in the headers... Yeah any approach would be ok, as long as we get the DB update seq, along with the local docs. I suggested headers/flag based solution so that none of the old client has any kind API problems, for backward compatibility in mind. Specifically the one which has some kind of checks in place for the data they receive rom couchdb. > With the `main` branch where sequences are global, it might be interesting to return both _local_seq and _db_seq so in one response we can tell when the document was updated relative to other documents, even in different databases on the same FDB cluster, and also, find out what the current db sequence is when this document was read. Absolutely!, will have many usefull cases. > Regarding the replication problem, I was wondering if connections are re-used if 1 vs 2 or 3 connection would have that much of an impact. Some time is spent during the SSL negotiation when setting up a new connection, but after that if the connection stays open there may not be a huge difference between having one or a few more requests. I am not able to understand this, not an expert on this matter. Are you suggesting that few steps of replication can be combined onto a single connections ? -- 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. For queries about this service, please contact Infrastructure at: [email protected]
