Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] Contribution of MQTT Servers (Mosquitto and RSMB)

This is great news!

Paul


On 24 June 2013 11:49, Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hello all,

both Roger and I are closer to being able to contribute our MQTT servers, Mosquitto and RSMB.  Roger has been talking to Mike Milinkovich about the right place for an MQTT server.  I admit, that this question had not occurred to me before, I had assumed that RSMB/Mosquitto would be contributed to Paho.

Questions

1) In which project should an MQTT server be placed?  The RT project is for runtimes, but focussed on Java technology (Equinox/OSGi).  M2M top level project, should it exist?

2) If both RSMB and Mosquitto code were contributed, how would we manage them?  One thought: have both codebases in a separate structure in the same source repository, then any merging of function can take place as required, no rush.  There is a difference between code being in a repository, and a component being released.

3) If someone contributed a Java MQTT server at some later date, which might be a better fit for Eclipse as a whole, would that cause us any problem?  I hope not.

Ian

_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev




--
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair, VP, Apache Synapse

UK: +44 207 096 0336
US: +1 646 595 7614

blog: http://pzf.fremantle.org
twitter.com/pzfreo
paul@xxxxxxxx

wso2.com Lean Enterprise Middleware

Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.

Back to the top