Skip to content

Implement connection types #6

@deavmi

Description

@deavmi

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.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingdocumentationImprovements or additions to documentationenhancementNew feature or request

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions