[GitHub] [incubator-pegasus] cauchy1988 commented on issue #840: add 'feature flags' rcp interface for version compatability between server and client

[GitBox <gi...@apache.org>]

cauchy1988 commented on issue #840:
URL: https://github.com/apache/incubator-pegasus/issues/840#issuecomment-1006312086


   > It seems that the negotiation is designed especially for the batchget3 interface or
   
   My idea is: the new server itself should be compatible with the old client, this is a common practice in the industry;
   in this issue I focus on solving the problem of compatibility with the old server when the new client develops new functions;
   Then answer your three questions above:
   1. old client-->new server: The new server itself needs to be compatible with the old server as mentioned above, so this is not a problem
   2. new client --> old server: as the method of this issue, downgraded to the old way of use
   3. Old server upgrade to new server: firstly, there is no problem with the old client continuing to use. secondly , the new client will follow the client's implementation plan in this issue: it will ensure that all downstream services support the new feature before sending the rpc of the new protocol  Request, otherwise use the old


-- 
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: dev-unsubscribe@pegasus.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pegasus.apache.org
For additional commands, e-mail: dev-help@pegasus.apache.org