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

D3.1.2 Interworking with Legacy Networks #179

Closed pchainho closed 7 years ago

pchainho commented 8 years ago

As required by T6.3 see https://github.com/reTHINK-project/dev-runtime-core/issues/107

antonroman commented 8 years ago

I'm working on the diagram to interwork reTHINK with Slack. The idea is to be able to send messages from reTHINK using real time messaging API. Checking also how the auth can be handled https://api.slack.com/docs/oauth

antonroman commented 7 years ago

I was considering the role of the IW Hyperty, which only role is to translate Data Object sync stream into Messages easier to translate into Legacy Domain protocol. Does it make sense to have it as an individual entity? Would it make sense to integrate it in the IW Protostub?

This would force the Hyperty using the IW protostub to associate to the Legacy domain identity and this is something that we want to avoid, isn't it?

Referencing the diagram, the Hyperty could be associated to antonroman at gmail.com and the Hyperty IW could be associated to @antonroman? Will this be a general case?

In the case of IMS, according to what we discussed yesterady the IMS authentication will be also based on a token, so it would be very similar to the integration to other legacy domains.

pchainho commented 7 years ago

As discussed today, I would also be in favor of avoiding the IW Hyperty but this would have impact in the core runtime namely: