Add version control to over-vmci protocol

[msterin]

VMCI protocol should include version # so we can prevent incompatible version of plugin and esx service from trying to talk

[govint]

Mark, is this version for the server? Or the format of data exchanged -args
and results format - between client and server over vmci. We may need
version for the server and client as well to handle new/old server with
new/old client.
On May 5, 2016 5:12 AM, "Mark Sterin" notifications@github.com wrote:

VMCI protocol should include version # so we can prevent incompatible
version of plugin and esx service from trying to talk

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#318

[govint]

May be we need the ESX service to support a get Version() API as well.
On May 5, 2016 10:20 AM, "Govindan T" tgovin1@gmail.com wrote:

Mark, is this version for the server? Or the format of data exchanged
-args and results format - between client and server over vmci. We may need
version for the server and client as well to handle new/old server with
new/old client.
On May 5, 2016 5:12 AM, "Mark Sterin" notifications@github.com wrote:

VMCI protocol should include version # so we can prevent incompatible
version of plugin and esx service from trying to talk

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#318

[govint]

Sorry, I wasn't clear. The version for the over-VMCI data is really for the
server only. The APIs and the args/results formats are defined by the
server. Having a version for that seems fine. In which case a server
getVersion() or 'null()' method call would help the client establish what
server-version its talking to.

On Thu, May 5, 2016 at 10:20 AM, Govindan T tgovin1@gmail.com wrote:

Mark, is this version for the server? Or the format of data exchanged
-args and results format - between client and server over vmci. We may need
version for the server and client as well to handle new/old server with
new/old client.
On May 5, 2016 5:12 AM, "Mark Sterin" notifications@github.com wrote:

VMCI protocol should include version # so we can prevent incompatible
version of plugin and esx service from trying to talk

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#318

[msterin]

@lipingxue - lets talk offline and see if it fits in your queue