Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible future works #85

Open
1 of 5 tasks
benedekh opened this issue Sep 4, 2017 · 1 comment
Open
1 of 5 tasks

Possible future works #85

benedekh opened this issue Sep 4, 2017 · 1 comment

Comments

@benedekh
Copy link
Member

benedekh commented Sep 4, 2017

  • implement new message formats, e.g. JSON, XML. As of now (04.09.2017) only protobuf is used.
  • enable different message formats to be used on the network in parallel. E.g. JSON, protobuf messages are being transferred through the network and each of them is correctly handled by the dispatchers
  • separate the messages for different channels on the MQTT transport. As of now (04.09.2017) every message goes to the /modes3/data channel, which might not be the best solution. Note that it might require changing the deployment scripts also. It looks like a big refactoring.
  • any other issues which are marked as wontfix on GitHub (first, check if they are still relevant)
  • any other issues which are marked as enhancement on GitHub (first, check if they are still relevant)
@benedekh
Copy link
Member Author

benedekh commented Sep 25, 2017

separate the messages for different channels on the MQTT transport. As of now (04.09.2017) every message goes to the /modes3/data channel, which might not be the best solution. Note that it might require changing the deployment scripts also. It looks like as a big refactoring.

is already implemented on the refactoring branch. --> update: it is merged into master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant