P2p specs

[pchainho]

Below, an impact analysis of phase 2 specs to support P2P message delivery, is provided. Extensions to phase 1 specs are highlighted with New!!. Responsibles named below, pls, have a look. The pull request will be merged by end of this week (23rd Sept).

• Runtime descriptor model with P2P Stub catalogue URLs: responsible: FOKUS @emmelmann-fokus
• Hyperty Registry model with Hyperty Runtime URL, its P2P Handler Stub instance URL and the catalogue URL of P2P Requester Stub. Responsible: INESC @rjflp
• Runtime deployment. Responsible: ALB @pchainho
• Hyperty Registry Responsible: INESC @Ricardo-Chaves
• Hyperty Discovery Responsible: INESC @Ricardo-Chaves
• Resolve Routing Address Responsible: INESC @Ricardo-Chaves
• deploy Protostub Responsible: ALB @pchainho
• P2P connection setup Responsible: ALB @pchainho
• Observer subscription procedure Responsible: ALB @pchainho

[emmelmann-fokus]

Paulo, can you please specify exactly what has to be done here.

[pchainho]

@emmelmann-fokus I've tried to make it more clear. Let me know if it is still not clear