| Re: [paho-dev] paho-dev Digest, Vol 18, Issue 17 |
Send paho-dev mailing list submissions to
paho-dev@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://dev.eclipse.org/mailman/listinfo/paho-dev
or, via email, send a message with subject or body 'help' to
paho-dev-request@xxxxxxxxxxx
You can reach the person managing the list at
paho-dev-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of paho-dev digest..."
Today's Topics:
1. Contribution of MQTT Servers (Mosquitto and RSMB) (Ian Craggs)
2. Re: Contribution of MQTT Servers (Mosquitto and RSMB)
(Mike Milinkovich)
3. Re: Contribution of MQTT Servers (Mosquitto and RSMB) (Ian Craggs)
4. Re: Contribution of MQTT Servers (Mosquitto and RSMB)
(Paul Fremantle)
----------------------------------------------------------------------
Message: 1
Date: Mon, 24 Jun 2013 11:49:49 +0100
From: Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx>
To: paho-dev@xxxxxxxxxxx
Subject: [paho-dev] Contribution of MQTT Servers (Mosquitto and RSMB)
Message-ID: <51C8244D.50904@xxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.eclipse.org/mailman/private/paho-dev/attachments/20130624/69d7e264/attachment.html>
------------------------------
Message: 2
Date: Mon, 24 Jun 2013 07:35:29 -0400
From: Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx>
To: General development discussions for paho project
<paho-dev@xxxxxxxxxxx>
Cc: "paho-dev@xxxxxxxxxxx" <paho-dev@xxxxxxxxxxx>
Subject: Re: [paho-dev] Contribution of MQTT Servers (Mosquitto and
RSMB)
Message-ID: <D8C54BD8-0ABA-4764-9DD9-E7363A9279DE@xxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Here is a suggestion. It is just a suggestion! Hopefully it can be improved upon.
. Put the server code in a separate component or sub-project under Paho. As you suggested, putting both in the same repository and merging them gradually makes sense.
. I think that there is value in the Mosquitto name. How would people feel about adopting that as the MQTT server "brand"?
I personally see no value in putting M2M runtimes in the EclipseRT project. Top-level projects are intended to group communities of interest, and there is no need to be pedantic about their scope.
If a Java implementation showed up later, they would be welcomed. As would Python, PHP or C#. It would be a nice problem to have.
Mike Milinkovich
+1.613.220.3223
mike.milinkovich@xxxxxxxxxxx
On 2013-06-24, at 6:49 AM, 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.eclipse.org/mailman/private/paho-dev/attachments/20130624/0cb2e9cb/attachment.html>
------------------------------
Message: 3
Date: Mon, 24 Jun 2013 14:07:01 +0100
From: Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx>
To: General development discussions for paho project
<paho-dev@xxxxxxxxxxx>
Subject: Re: [paho-dev] Contribution of MQTT Servers (Mosquitto and
RSMB)
Message-ID: <51C84475.3070303@xxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Personally, I am happy to adopt Mosquitto as the MQTT server 'brand'.
Really Small Message Broker was a name coined for IBM alphaWorks. The
requirements for such names are that they are descriptive more than
memorable, so that no or limited trademark search was required, so I
always felt it was a stop gap name. (The original name was nanobroker,
but that trademark was already owned).
I am also happy to have the server code under Paho, as that would solve
my testing 'problem' too. That is, to test the clients, we need a
server to test against. If we build a both server and clients as part
of the Paho, then it makes it easier to test both clients and server.
(I thought that Roger had indicated that some other location had been
discussed for Mosquitto).
Ian
On 06/24/2013 12:35 PM, Mike Milinkovich wrote:
>
> Here is a suggestion. It is just a suggestion! Hopefully it can be
> improved upon.
>
> . Put the server code in a separate component or sub-project under
> Paho. As you suggested, putting both in the same repository and
> merging them gradually makes sense.
> . I think that there is value in the Mosquitto name. How would people
> feel about adopting that as the MQTT server "brand"?
>
> I personally see no value in putting M2M runtimes in the EclipseRT
> project. Top-level projects are intended to group communities of
> interest, and there is no need to be pedantic about their scope.
>
> If a Java implementation showed up later, they would be welcomed. As
> would Python, PHP or C#. It would be a nice problem to have.
>
> Mike Milinkovich
> +1.613.220.3223
> mike.milinkovich@xxxxxxxxxxx <mailto:mike.milinkovich@xxxxxxxxxxx>
>
> On 2013-06-24, at 6:49 AM, Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto: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 <mailto:paho-dev@xxxxxxxxxxx>
>> http://dev.eclipse.org/mailman/listinfo/paho-dev
>
>
> _______________________________________________
> paho-dev mailing list
> paho-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/paho-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.eclipse.org/mailman/private/paho-dev/attachments/20130624/999ded84/attachment.html>
------------------------------
Message: 4
Date: Mon, 24 Jun 2013 14:12:29 +0100
From: Paul Fremantle <paul@xxxxxxxx>
To: General development discussions for paho project
<paho-dev@xxxxxxxxxxx>
Subject: Re: [paho-dev] Contribution of MQTT Servers (Mosquitto and
RSMB)
Message-ID:
<CAGswUzzhO2_SW1RDPpJomFj9uea-qx9H92YRcG639DjUFm3Esg@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.eclipse.org/mailman/private/paho-dev/attachments/20130624/9a8e0a44/attachment.html>
------------------------------
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev
End of paho-dev Digest, Vol 18, Issue 17
****************************************