Runtime Registry: P2P Protostubs support

[pchainho]

• [x] Hyperty deployment extension for P2P connections
• [x] Hyperty and Data object Registry model extension for P2P connections
• [x] Address Resolution extension for P2P connections
• [x] Hyperty Discovery extension for P2P connections

[vitormsilva]

Hi, I have a problem with the P2P resolve. When a hyperty is registred, and the messages will be send to other hyperty, i always have checkHypertyP2PHandler don't find any hyperty.

Could you check the registerHyperty and from step 6 to step 22 here.

If you need help, we can try to help you..

[vitormsilva]

I found other problem.. I don't know if it's related to, but seems have some "fake" data, in these case to register dataObjects.

[tiagolb]

That error message comes from a reject in the checkHypertyP2pHandler function which is responsible for searching in the local cache for a p2phandler and if no p2phandler is foound it should trigger a discovery process (step 9 to step 14 of the spec).

But this discovery process is not yet done. I'm looking into it.

[tiagolb]

@BernardoMG The function to be modified in order to support the discovery service for finding the p2pHandler is called checkHypertyP2pHandler in line 800 of the Registry.js. There's a TODO comment in that line where the discovery process must be triggered.

[BernardoMG]

@tiagolb Currently I'm working on some issues on Domain Registry, i will see that as soon as I can.

[BernardoMG]

@vitormsilva @tiagolb Already implemented the discovery process in checkHypertyP2PHandler. The changes are in dev-p2pbranch. It's necessary to use the branch connector-release-0.6.0 in dev-msg-node-vertx.

[pchainho]

pls in case they are complete, update the the tasks list above and close the issue if everything is done. Otherwise comment here what is missing

[pchainho]

Done