Suggestion: JSON-RPC method namespace

[cpriest]

Add a namespace field the JSON message to namespace the method calls.

For example, all messages from the specification might be "lp-spec.01"

This way:

• Method names won't have to worry about clashing with any existing plugin or launcher method names
• Method names could be (if desired) versioned (as shown above)

[tzickel]

There are 2 questions here:

1. What should be passed in the negotiation part at startup (currently the server sends a list of apiversions and the client selects one, but maybe it could select a few?).
2. How to encode versioning of specific Messages (which convey a flow from a specific version of the specification), I am leaning towards encoding the version / namespace in the message name itself (or maybe in the http headers as a content-type).

[cpriest]

I'm not familiar with the JSON-RPC spec, but based on the example in your main document, can we just add a namespace root-level parameter?

[tzickel]

The spec is as linked in the document: https://en.wikipedia.org/wiki/JSON-RPC#Usage The reason to follow it is that there are tons of libraries for many languages which implement this way of talking, for example vscode-jsonrpc package: https://github.com/tzickel/lps-playground/blob/master/nodejs/pluginbridge.js#L55 Gives us with zero effort the ability to parse and handle this communication method.