Shuo-Jia commented on issue #840: URL: https://github.com/apache/incubator-pegasus/issues/840#issuecomment-998710744
> Hower the client side may be a little difficult, and even for me it’s a bit vague to what extent the function needs to be implemented, the following pdf is the java client side design I have thought of > [feature negotiation client side simple design.pdf](https://github.com/apache/incubator-pegasus/files/7656247/feature.negotiation.client.side.simple.design.pdf) I notice that the `negotiation` seem to be apply to `meta` and `replica`, I consider whether just `negotiation` with `meta` to fetch the feature supporting list. we don't have to handle the different version among `replica`, `meta` can represents the current cluster version. if client request is not supported by replica server, replica server will return error, and triger update `meta` config update. Of course, the meta server need upgrade at last , I think it can be acceptable. Just consider `meta` maybe let your implement more simple. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
