D3.1.2 Messaging Framework (Update summary)

[pchainho]

Reference material:

• MN Spec
• Messaging Framework tutorial

[pchainho]

see template proposal at #172

[sdruesedow]

just to keep track of some thoughts and issues:

Idm Connector:

• unclear role and weak description in phase 1
• was mentioned in original description but without any specification
• no implementation in any MN --> Proposal: either remove or provide a clear role description and specification for phase 2

End-user device and network server connectors:

• description of both was very weak in D3.1
• unclear separation from ProtocolStub mechanism
• no special implementation in any MN
• MN specific descriptions stated them as done by the stubs --> Proposal: remove them as individual architectural blocks

Global Registry Connector:

• present in the Vertx MN
• role, use-cases and specification are unclear --> Proposal: provide use-case and specification

[sdruesedow]

summarized results from WP3 telco: IDM-connector:

• intended to support access control to the MN
• not implemented yet
• but keep it in the architecture picture and update the description

end-user device and network-server connector:

• these are actually the server-side endpoints of the stub-connections (i.e. WS server)
• conceptually they could be different, but implementation wise they are currently the same component in the MN architecture
• keep them in the architecture picture, move them closer to the ProtoStub
• update the descriptions

Global Registry connector

• should be handled comparable to the domain registry connector
• add this to the architecture picture --> provide initial description with links to the specified messages
• several open questions --> open separate issue for that

[pchainho]

Any updates to detailed specs should be provided here in the new specs repo

[pchainho]

I've just noticed we have lots of very good material here that probably would fit better here

[sdruesedow]

This is the structure of the Messaging Framework chapter with links to the corresponding content:

2.2.1 Hyperty Messaging Framework Overview https://github.com/reTHINK-project/specs/blob/master/messaging-framework/readme.md (without the 4 sub-sections that are linked at the bottom of this page)

2.2.2 Protocol on-the-fly https://github.com/reTHINK-project/specs/blob/master/messaging-framework/protofly.md

2.2.3 Data Synchronization mechanism (Reporter-Observer) https://github.com/reTHINK-project/specs/blob/master/messaging-framework/p2p-data-sync.md

2.2.4 Messaging Node 2.2.4.1 Functional Architecture https://github.com/reTHINK-project/specs/blob/master/messaging-framework/msg-node.md

2.2.4.2 General design considerations https://github.com/reTHINK-project/specs/blob/master/messaging-framework/msg-node-design.md

2.2.4.3 Stub specification https://github.com/reTHINK-project/specs/blob/master/messaging-framework/stub-specification.md

2.2.4.4 Available reference Implementations tbd: Just a short list of the available implementations with links to their documentation.

2.2.4.5 Recommendations https://github.com/reTHINK-project/specs/blob/master/tutorials/msg-node-development-recommendations.md