Previously the method of identifying whether a connection was another server or a client would be done per message with the scope identifier but this will lead to ambiguities.
I want to perhaps introduce that upon connection the protocol spec (v2) will have to incorporate the following:
"identify' : {"scope" : "client/server"}
If the "scope" field is set to "client" then another field "authentication" must be present, else the connection gets closed.
If the "scope" field is set to "server" then no authentication is required and the connection can be handled.
Previously the method of identifying whether a connection was another server or a client would be done per message with the
scopeidentifier but this will lead to ambiguities.I want to perhaps introduce that upon connection the protocol spec (
v2) will have to incorporate the following:If the
"scope"field is set to"client"then another field"authentication"must be present, else the connection gets closed.If the
"scope"field is set to"server"then no authentication is required and the connection can be handled.