etonkin
commented
6 years ago Hi,
MQTT should be an optional feature I would say (configurable but not required). Just another logging method in a pile of possible methods. It is possibly something that in a different environment I would recommend configuring via syslog/syslog-ng rather than directly in hyperstream at all.
To do that meaningfully/safely we'd need to have a good grasp of the various sorts of information that HyperStream might log.
On 22 February 2018 at 11:02, Miquel Perelló Nieto <notifications@github.com
wrote:
It is not clear to me what is the role of MQTT in a general framework as HyperStream. I understand that the original reason is because of our internal use in an Internet of Thinks environment where communication is driven by MQTT, but this requirement may be a barrier for the general user.
Would you think it should be activated optionally or change it to a plugin?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/IRC-SPHERE/HyperStream/issues/31, or mute the thread https://github.com/notifications/unsubscribe-auth/AEwgBFegjILh6yZp4cS_hLb8uZ9Td0Ueks5tXUlTgaJpZM4SPHq5 .
tdiethe
It is not clear to me what is the role of MQTT in a general framework as HyperStream. I understand that the original reason is because of our internal use in an Internet of Thinks environment where communication is driven by MQTT, but this requirement may be a barrier for the general user.
Would you think it should be activated optionally or change it to a plugin?
If it is really a required part of HyperStream, we should advertise it in this context then.