search

reTHINK-project / core-framework

The main goal of WP3 is to provide the reTHINK core framework comprised by the runtime environment where Hyperties are executed and the messaging nodes used to support messages exchange between Hyperties.
Apache License 2.0
1 stars 0 forks source link

Managing Hyperty disconnection #167

Open avallee-apizee opened 8 years ago

avallee-apizee commented 8 years ago

The question we have is how the rethink framework manages hyperty disconnection (like when there is a network issue or even simply closing the browser).

How the subscriber to the data object gets informed of the disconnection ? Who is going to provide and broadcast this information ?

pchainho commented 8 years ago

At this point I see the following options:

  1. the message node detects the runtime was disconnected
  2. the extension of keep registration alive
  3. having a network side hyperty periodically pooling the runtime registry

In principle I would be in favor of option 2, since it will be easier to implement (runtime registry has all the information required) and will not depend on the protocol used by the message node. Option 1 probably has less costs in terms of traffic and computation but would be more difficult to implement and would create another requirement to be fulfilled by message nodes.