Difference between revisions of "Paho/Repository"

From Eclipsepedia

Jump to: navigation, search
(initial page to start the discussion.)
 
(updated to match current repos)
 
(3 intermediate revisions by one user not shown)
Line 1: Line 1:
 
== Paho Git Repository structure  ==
 
== 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.
+
The Paho project is relatively new and the repository structure is still evolving. Here is the current structure and proposals for additional things that are coming along.
  
{| width="400" border="1" cellpadding="1" cellspacing="1"
+
{| width="500" border="1" cellpadding="1" cellspacing="1"
 
|-
 
|-
 
| '''Location'''  
 
| '''Location'''  
 
| '''Description'''
 
| '''Description'''
|-
+
| '''comments'''
| org.eclipse.paho.mqtt.git
+
| Top-level MQTT packages
+
 
|-
 
|-
 
| org.eclipse.paho.mqtt.c.git  
 
| org.eclipse.paho.mqtt.c.git  
 
| MQTT Client Package - C Language
 
| MQTT Client Package - C Language
 +
|
 
|-
 
|-
 
| org.eclipse.paho.mqtt.java.git  
 
| org.eclipse.paho.mqtt.java.git  
 
| MQTT Client Package - Java Language
 
| MQTT Client Package - Java Language
 +
|
 
|-
 
|-
 
| org.eclipse.paho.mqtt.lua.git  
 
| org.eclipse.paho.mqtt.lua.git  
 
| MQTT Client Package - Lua Language
 
| 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''
 
|}
 
|}
  
org.eclipse.paho.apps.git MQTT sample and example applications (note: right now, the clients contain their own samples so what is this for?)
 
  
org.eclipse.paho.esf.git MQTT Application Framework (''question - 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. We should pull the C examples out of the docs and into the repository.
 +
 +
Utilities (Ian C mentioned a trace utility)
 +
 +
MQTT Wireshark plugin (there are a couple of them, incomplete)
  
 +
Test suite / protocol compliance suite.
  
=== Future needs ===
+
Additional clients (target languages? Python, Perl, PHP...?)
  
Broker - this might be written in C (mosquitto?), or some other language (Java/OSGi). So possibly need 2 trees?
+
Further IDE tools
  
Samples
+
=== Discussion  ===
  
Additional clients
+
#Paho may not only contain MQTT clients so having a org.eclipse.paho.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)
 +
#...

Latest revision as of 18:44, 11 March 2013

[edit] Paho Git Repository structure

The Paho project is relatively new and 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.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


[edit] 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. We should pull the C examples out of the docs and into the repository.

Utilities (Ian C mentioned a trace utility)

MQTT Wireshark plugin (there are a couple of them, incomplete)

Test suite / protocol compliance suite.

Additional clients (target languages? Python, Perl, PHP...?)

Further IDE tools

[edit] Discussion

  1. Paho may not only contain MQTT clients so having a org.eclipse.paho.mqtt. level makes sense
  2. 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)
  3. ...