Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Paho/Project Plan"
< Paho
(added proposed high level release milestones) |
|||
| (37 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | = [https://projects.eclipse.org/projects/iot.paho/documentation Current Plan] = | |
| − | + | The release plans are in the project documentation - see "releases" at https://projects.eclipse.org/projects/iot.paho/documentation. | |
| − | + | * [https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&classification=Technology&component=MQTT&component=Samples&component=Sandbox&list_id=3090526&product=Paho&query_format=advanced&order=bug_status%2Cpriority%2Cbug_severity list of open Paho bugs] | |
| − | + | == Current and Near Future Major Items == | |
| − | + | * contributing to M2Mqtt: regression tests, disk persistence, maybe some other items | |
| + | * offline buffering (ability to send while not connected) and automatic reconnect for C, Java and JavaScript clients | ||
| + | * ongoing embedded client improvements: proper FreeRTOS support, asynchronous clients, build improvements, documentation: porting guides, tutorials, formal MQTTClient-C release | ||
| + | * Android service stability, Android app | ||
| + | * WebSockets support for C, Python clients (any others?) | ||
| + | * MQTT-SN to MQTT embedded gateway | ||
| + | * MQTT conformance test material | ||
| + | * MQTT client statistics | ||
| + | * possibly an MQTT forwarder for DMZ (it's been mooted, but I'm not exactly sure what it means) | ||
| − | + | === Actively Soliciting Contributions for === | |
| − | + | It would be nice for Paho to have these, even if they do already exist elsewhere. Eclipse legal processes mean that the software is clean, safe to use commercially. | |
| − | == | + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=442878 PHP client] |
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=442877 Ruby client] | ||
| + | * Node.js client | ||
| − | + | == Directions == | |
| − | + | * Expand client library coverage to all major programming languages (http://spectrum.ieee.org/computing/software/top-10-programming-languages) | |
| − | + | * I am assuming the MQTT specification will evolve over the next couple of years. Would it make sense to start an incubator to try out some new ideas for the spec? Developers could contribute code that implements these ideas and this would help the MQTT TC in the evolution of the spec. (Ian Skerrett) | |
| + | Paho incubator has now been created - https://projects.eclipse.org/projects/iot.paho.incubator | ||
| − | = | + | * I'd like to see a focus on creating tools to test/debug/deploy MQTT apps. Tools like MQTTLens I think will be critical to the adoption of MQTT. Could Paho be the home to these types of tools? (Ian Skerrett) |
| + | Add suggestions here [https://bugs.eclipse.org/bugs/show_bug.cgi?id=442874 Ideas for tools that could be created or adopted to test/debug/deploy MQTT] | ||
| − | + | * I think the MQTT embedded security story could be greatly improved (Julien Vermillard) I think today using MQTT or any M2M protocol with security on any embedded platform is difficult and cumbersome. I use wakaama with tinydtls a DTLS implementation MIT licensed and at some point I would like to provide ready to install client on some platform but with security (with a business friendly license) as a mandatory feature. Maybe it worth looking at http://axtls.sourceforge.net/ (BSD licensed) or extending tinydtls for providing good old TLS which is in fact simpler than DTLS. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 06:09, 11 November 2015
Contents
Current Plan
The release plans are in the project documentation - see "releases" at https://projects.eclipse.org/projects/iot.paho/documentation.
Current and Near Future Major Items
- contributing to M2Mqtt: regression tests, disk persistence, maybe some other items
- offline buffering (ability to send while not connected) and automatic reconnect for C, Java and JavaScript clients
- ongoing embedded client improvements: proper FreeRTOS support, asynchronous clients, build improvements, documentation: porting guides, tutorials, formal MQTTClient-C release
- Android service stability, Android app
- WebSockets support for C, Python clients (any others?)
- MQTT-SN to MQTT embedded gateway
- MQTT conformance test material
- MQTT client statistics
- possibly an MQTT forwarder for DMZ (it's been mooted, but I'm not exactly sure what it means)
Actively Soliciting Contributions for
It would be nice for Paho to have these, even if they do already exist elsewhere. Eclipse legal processes mean that the software is clean, safe to use commercially.
- PHP client
- Ruby client
- Node.js client
Directions
- Expand client library coverage to all major programming languages (http://spectrum.ieee.org/computing/software/top-10-programming-languages)
- I am assuming the MQTT specification will evolve over the next couple of years. Would it make sense to start an incubator to try out some new ideas for the spec? Developers could contribute code that implements these ideas and this would help the MQTT TC in the evolution of the spec. (Ian Skerrett)
Paho incubator has now been created - https://projects.eclipse.org/projects/iot.paho.incubator
- I'd like to see a focus on creating tools to test/debug/deploy MQTT apps. Tools like MQTTLens I think will be critical to the adoption of MQTT. Could Paho be the home to these types of tools? (Ian Skerrett)
Add suggestions here Ideas for tools that could be created or adopted to test/debug/deploy MQTT
- I think the MQTT embedded security story could be greatly improved (Julien Vermillard) I think today using MQTT or any M2M protocol with security on any embedded platform is difficult and cumbersome. I use wakaama with tinydtls a DTLS implementation MIT licensed and at some point I would like to provide ready to install client on some platform but with security (with a business friendly license) as a mandatory feature. Maybe it worth looking at http://axtls.sourceforge.net/ (BSD licensed) or extending tinydtls for providing good old TLS which is in fact simpler than DTLS.