Domain Registry: notification about entities that are back to live

[pchainho]

Currently, the setup of sync data streams requires that all involved peers (reporters and observer) are all connected. Otherwise, invitations and subscriptions will be lost.

In order to support "delayed" setup of sync data streams it is required that unregistration of Hyperties and Data Objects will not delete these entries from the Domain Registry but change its status to "disconnected". Then, when a search is made a "480 Temporarily Unavailable" should be responded with the registered URL in the message Body. As soon as the Hyperty is back online, the status will be updated to "live".

The Hyperty or the App that receives the 480 response message has the option to request the Domain Registry to be notified when the Hyperty or the Object will be back to live.

The assumption is that addresses of hyperties and data objects will be reused as specified at #6.

[pchainho]

As discussed last week, each registered entity will have an associated address that will be used by the domain registry to publish its registration status through the Message Node bus. The proposal is: <registryEntityURL>/registration .

Any other entity can request to be notified about changes on this registration status by sending a subscription request to MN Subscription Manager address.

[pchainho]

I've just added the specs for the messages:

• publish change to disconnected
• publish change to live
• subscribe to be notified about changes on the registration status