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/Repository"
< Paho
(→Paho Git Repository structure) |
(→Future needs: added discussion) |
||
| Line 36: | Line 36: | ||
| − | === Future needs === | + | === Future needs === |
| − | Broker - this might be written in C (mosquitto?), or some other language (Java/OSGi). So possibly need 2 trees? | + | Broker - this might be written in C (mosquitto proposed?), or some other language (Java/OSGi). So possibly need 2 trees? or would it be a separate project from Paho? (see discussion) |
Samples | Samples | ||
| − | Additional clients | + | Utilities (Ian C mentioned a trace utility) |
| + | |||
| + | Additional clients (target languages? Python, Perl, PHP...?) | ||
| + | |||
| + | Further IDE tools | ||
| + | |||
| + | === Discussion === | ||
| + | |||
| + | #Paho may not only contain MQTT clients so having a org.eclipse.mqtt. level makes sense | ||
| + | #should all of the client packages be under a .clients. tree rather than having a language-based split at the top level? (this would enable a parallel .brokers. tree with language-specific stuff in future) | ||
| + | #... | ||
Revision as of 09:11, 12 June 2012
Paho Git Repository structure
Since the Paho project is new, the repository structure is still evolving. Here is the current structure and proposals for additional things that are coming along.
| Location | Description | comments |
| org.eclipse.paho.mqtt.git | Top-level MQTT packages | |
| org.eclipse.paho.mqtt.c.git | MQTT Client Package - C Language | |
| org.eclipse.paho.mqtt.java.git | MQTT Client Package - Java Language | |
| org.eclipse.paho.mqtt.lua.git | MQTT Client Package - Lua Language | |
| org.eclipse.paho.apps.git | MQTT sample and example applications | right now, the clients contain their own samples so what is this for? |
| org.eclipse.paho.esf.git | MQTT Application Framework | is this an appropriate name? ESF = Eurotech so I guess we want a more generic name |
Future needs
Broker - this might be written in C (mosquitto proposed?), or some other language (Java/OSGi). So possibly need 2 trees? or would it be a separate project from Paho? (see discussion)
Samples
Utilities (Ian C mentioned a trace utility)
Additional clients (target languages? Python, Perl, PHP...?)
Further IDE tools
Discussion
- Paho may not only contain MQTT clients so having a org.eclipse.mqtt. level makes sense
- should all of the client packages be under a .clients. tree rather than having a language-based split at the top level? (this would enable a parallel .brokers. tree with language-specific stuff in future)
- ...