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

What is the correct format of a reTHINK message? #138

Closed sdruesedow closed 8 years ago

sdruesedow commented 8 years ago

Do the "id", "type", "from" and "to" fields need to be wrapped in a "header" object or not?

The examples in the specs currently don't do it, but the Vertx implementations does. Which one is the agreed format?

pchainho commented 8 years ago

there is no Header message object. Vertx dev branch should already be aligned with the message specs

sdruesedow commented 8 years ago

OK, thanks!

acheambe commented 8 years ago

I had this question a while back too. Example of a reTHINK message format created by the message factory looks like this.

{"id":"8b5f8e86-1a5f-4025-a4d7-1c47c819bf3a","from":"hyperty-runtime-esn://domain.com/12345","to":"[hyperty-runtime-imei://domain.com/12345, hyperty-runtime-imei://domain.com/678910]","type":"create","contextId":"a7317660-bfa1-4830-b03f-278a814d2feb","signature":null,"body":{"accessToken":null,"resource":"hyperty-runtime-uuid://domain.com/myResource","value":"{audio: 'PCMU-Codec'}","policy":"policyURL"}}

Please anyone, shout if this format is wrong.