You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Christian Schneider <ch...@die-schneider.net> on 2016/03/24 14:42:12 UTC
[Discuss] Chronicle Queue transport for Aries rsa (licensing)
I just did a POC Aries rsa transport using Chronicle Queue. It is indeed
very fast. I get about 500 000 msg/s for one way calls.
So from a performance perspective I think it would be very interesting
to have this as a transport.
I am not sure if their licensing works for us though. They have switched
to lgpl mid last year.
The good news is that I was able to get Peter Lawrey to add a special
licensing for open source projects like Aries.
See: https://github.com/OpenHFT/Chronicle-Queue/issues/250
and:
https://github.com/OpenHFT/Chronicle-Queue/blob/master/LICENSE%20for%20Open%20Source%20product%20usage.txt
So we are allowed to use the software under the apache license. Is that
good enough for us to include Chronicle queues into Aries rsa?
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [Discuss] Chronicle Queue transport for Aries rsa (licensing)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi David,
I wasn't clear: I don't mind about the dual license, I mind about the
current Apache license terms ;)
I would prefer a complete Apache license switch without any condition.
Regards
JB
On 03/25/2016 09:31 PM, David Bosschaert wrote:
> On 25 March 2016 at 08:07, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
>>
>> it's what I said in my other e-mail: we should wait that Chronicle fully
>> switches to Apache (and not dual license).
>>
>
> Dual-license is generally not a problem, I think. If a project is
> dual-licensed, for example being both LGPL and ASL licensed (without any
> further restrictions) then it is fully ASL licensed. AFAIK this is fine.
>
> The thing that is not fine is when they say it's ASL licensed but only
> under certain conditions...
>
> Cheers,
>
> David
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [Discuss] Chronicle Queue transport for Aries rsa (licensing)
Posted by David Bosschaert <da...@gmail.com>.
On 25 March 2016 at 08:07, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> it's what I said in my other e-mail: we should wait that Chronicle fully
> switches to Apache (and not dual license).
>
Dual-license is generally not a problem, I think. If a project is
dual-licensed, for example being both LGPL and ASL licensed (without any
further restrictions) then it is fully ASL licensed. AFAIK this is fine.
The thing that is not fine is when they say it's ASL licensed but only
under certain conditions...
Cheers,
David
Re: [Discuss] Chronicle Queue transport for Aries rsa (licensing)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Christian,
it's what I said in my other e-mail: we should wait that Chronicle fully
switches to Apache (and not dual license).
If they already plan to go to Apache license, IMHO, it doesn't make
sense to use another cat B license: they just have to go to Apache
license if they agree with.
Regards
JB
On 03/25/2016 09:05 AM, Christian Schneider wrote:
> As far as I understand it a downstream project would be able to use
> chronicle under apache license if it is open source itself.
> So it would create problems when integrating Aries rsa into a commercial
> product.
>
> I talked to Dan Kulp yesterday and he said that this is a field of use
> restriction that is not allowed at apache. Is that correct?
> If yes we would have to decline and ask Peter if they are willing to
> switch back to Apache License completely. Another possible solution
> brought up by Dan was that they could choose a suitable category b
> license if they want to exercise more control over their software while
> allowing apache use.
>
> Christian
>
>
> On 24.03.2016 15:15, David Bosschaert wrote:
>> Hi Christian,
>>
>> If they relicense for Aries to ASL I would still have the question
>> whether
>> I as a user of Aries in some different project can still use this library
>> under ASL. I mean is the relicensing only valid in the context of the
>> Aries
>> project or also in the context of other unrelated downstream projects or
>> products that use RSA from Aries?
>>
>> Cheers,
>>
>> David
>>
>> On 24 March 2016 at 13:42, Christian Schneider <ch...@die-schneider.net>
>> wrote:
>>
>>> I just did a POC Aries rsa transport using Chronicle Queue. It is indeed
>>> very fast. I get about 500 000 msg/s for one way calls.
>>> So from a performance perspective I think it would be very
>>> interesting to
>>> have this as a transport.
>>>
>>> I am not sure if their licensing works for us though. They have switched
>>> to lgpl mid last year.
>>>
>>> The good news is that I was able to get Peter Lawrey to add a special
>>> licensing for open source projects like Aries.
>>> See: https://github.com/OpenHFT/Chronicle-Queue/issues/250
>>> and:
>>> https://github.com/OpenHFT/Chronicle-Queue/blob/master/LICENSE%20for%20Open%20Source%20product%20usage.txt
>>>
>>>
>>> So we are allowed to use the software under the apache license. Is that
>>> good enough for us to include Chronicle queues into Aries rsa?
>>>
>>> Christian
>>>
>>> --
>>> Christian Schneider
>>> http://www.liquid-reality.de
>>>
>>> Open Source Architect
>>> http://www.talend.com
>>>
>>>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [Discuss] Chronicle Queue transport for Aries rsa (licensing)
Posted by Christian Schneider <ch...@die-schneider.net>.
As far as I understand it a downstream project would be able to use
chronicle under apache license if it is open source itself.
So it would create problems when integrating Aries rsa into a commercial
product.
I talked to Dan Kulp yesterday and he said that this is a field of use
restriction that is not allowed at apache. Is that correct?
If yes we would have to decline and ask Peter if they are willing to
switch back to Apache License completely. Another possible solution
brought up by Dan was that they could choose a suitable category b
license if they want to exercise more control over their software while
allowing apache use.
Christian
On 24.03.2016 15:15, David Bosschaert wrote:
> Hi Christian,
>
> If they relicense for Aries to ASL I would still have the question whether
> I as a user of Aries in some different project can still use this library
> under ASL. I mean is the relicensing only valid in the context of the Aries
> project or also in the context of other unrelated downstream projects or
> products that use RSA from Aries?
>
> Cheers,
>
> David
>
> On 24 March 2016 at 13:42, Christian Schneider <ch...@die-schneider.net>
> wrote:
>
>> I just did a POC Aries rsa transport using Chronicle Queue. It is indeed
>> very fast. I get about 500 000 msg/s for one way calls.
>> So from a performance perspective I think it would be very interesting to
>> have this as a transport.
>>
>> I am not sure if their licensing works for us though. They have switched
>> to lgpl mid last year.
>>
>> The good news is that I was able to get Peter Lawrey to add a special
>> licensing for open source projects like Aries.
>> See: https://github.com/OpenHFT/Chronicle-Queue/issues/250
>> and:
>> https://github.com/OpenHFT/Chronicle-Queue/blob/master/LICENSE%20for%20Open%20Source%20product%20usage.txt
>>
>> So we are allowed to use the software under the apache license. Is that
>> good enough for us to include Chronicle queues into Aries rsa?
>>
>> Christian
>>
>> --
>> Christian Schneider
>> http://www.liquid-reality.de
>>
>> Open Source Architect
>> http://www.talend.com
>>
>>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [Discuss] Chronicle Queue transport for Aries rsa (licensing)
Posted by David Bosschaert <da...@gmail.com>.
Hi Christian,
If they relicense for Aries to ASL I would still have the question whether
I as a user of Aries in some different project can still use this library
under ASL. I mean is the relicensing only valid in the context of the Aries
project or also in the context of other unrelated downstream projects or
products that use RSA from Aries?
Cheers,
David
On 24 March 2016 at 13:42, Christian Schneider <ch...@die-schneider.net>
wrote:
> I just did a POC Aries rsa transport using Chronicle Queue. It is indeed
> very fast. I get about 500 000 msg/s for one way calls.
> So from a performance perspective I think it would be very interesting to
> have this as a transport.
>
> I am not sure if their licensing works for us though. They have switched
> to lgpl mid last year.
>
> The good news is that I was able to get Peter Lawrey to add a special
> licensing for open source projects like Aries.
> See: https://github.com/OpenHFT/Chronicle-Queue/issues/250
> and:
> https://github.com/OpenHFT/Chronicle-Queue/blob/master/LICENSE%20for%20Open%20Source%20product%20usage.txt
>
> So we are allowed to use the software under the apache license. Is that
> good enough for us to include Chronicle queues into Aries rsa?
>
> Christian
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>
Re: [Discuss] Chronicle Queue transport for Aries rsa (licensing)
Posted by Christian Schneider <ch...@die-schneider.net>.
I just got feedback that a new release is planned for this week. I will add
the prototype then.
There is one caveat with the transport though. The open source chronicle
queue only supports local queues. Only the enterprise version has
distribution of the data over nodes.
Christian
2016-03-30 15:49 GMT+02:00 David Bosschaert <da...@gmail.com>:
> Sounds great!
>
> David
>
> On 30 March 2016 at 14:30, Daniel Kulp <dk...@apache.org> wrote:
>
> > Looks like on master they have completely switched to the Apache License.
> > Once they get a release with that, it would be usable. :)
> >
> > Dan
> >
> >
> >
> > > On Mar 24, 2016, at 9:42 AM, Christian Schneider <
> > chris@die-schneider.net> wrote:
> > >
> > > I just did a POC Aries rsa transport using Chronicle Queue. It is
> indeed
> > very fast. I get about 500 000 msg/s for one way calls.
> > > So from a performance perspective I think it would be very interesting
> > to have this as a transport.
> > >
> > > I am not sure if their licensing works for us though. They have
> switched
> > to lgpl mid last year.
> > >
> > > The good news is that I was able to get Peter Lawrey to add a special
> > licensing for open source projects like Aries.
> > > See: https://github.com/OpenHFT/Chronicle-Queue/issues/250
> > > and:
> >
> https://github.com/OpenHFT/Chronicle-Queue/blob/master/LICENSE%20for%20Open%20Source%20product%20usage.txt
> > >
> > > So we are allowed to use the software under the apache license. Is that
> > good enough for us to include Chronicle queues into Aries rsa?
> > >
> > > Christian
> > >
> > > --
> > > Christian Schneider
> > > http://www.liquid-reality.de
> > >
> > > Open Source Architect
> > > http://www.talend.com
> > >
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org - http://dankulp.com/blog
> > Talend Community Coder - http://coders.talend.com
> >
> >
>
--
--
Christian Schneider
http://www.liquid-reality.de
<https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.liquid-reality.de>
Open Source Architect
http://www.talend.com
<https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.talend.com>
Re: [Discuss] Chronicle Queue transport for Aries rsa (licensing)
Posted by David Bosschaert <da...@gmail.com>.
Sounds great!
David
On 30 March 2016 at 14:30, Daniel Kulp <dk...@apache.org> wrote:
> Looks like on master they have completely switched to the Apache License.
> Once they get a release with that, it would be usable. :)
>
> Dan
>
>
>
> > On Mar 24, 2016, at 9:42 AM, Christian Schneider <
> chris@die-schneider.net> wrote:
> >
> > I just did a POC Aries rsa transport using Chronicle Queue. It is indeed
> very fast. I get about 500 000 msg/s for one way calls.
> > So from a performance perspective I think it would be very interesting
> to have this as a transport.
> >
> > I am not sure if their licensing works for us though. They have switched
> to lgpl mid last year.
> >
> > The good news is that I was able to get Peter Lawrey to add a special
> licensing for open source projects like Aries.
> > See: https://github.com/OpenHFT/Chronicle-Queue/issues/250
> > and:
> https://github.com/OpenHFT/Chronicle-Queue/blob/master/LICENSE%20for%20Open%20Source%20product%20usage.txt
> >
> > So we are allowed to use the software under the apache license. Is that
> good enough for us to include Chronicle queues into Aries rsa?
> >
> > Christian
> >
> > --
> > Christian Schneider
> > http://www.liquid-reality.de
> >
> > Open Source Architect
> > http://www.talend.com
> >
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
Re: [Discuss] Chronicle Queue transport for Aries rsa (licensing)
Posted by Daniel Kulp <dk...@apache.org>.
Looks like on master they have completely switched to the Apache License. Once they get a release with that, it would be usable. :)
Dan
> On Mar 24, 2016, at 9:42 AM, Christian Schneider <ch...@die-schneider.net> wrote:
>
> I just did a POC Aries rsa transport using Chronicle Queue. It is indeed very fast. I get about 500 000 msg/s for one way calls.
> So from a performance perspective I think it would be very interesting to have this as a transport.
>
> I am not sure if their licensing works for us though. They have switched to lgpl mid last year.
>
> The good news is that I was able to get Peter Lawrey to add a special licensing for open source projects like Aries.
> See: https://github.com/OpenHFT/Chronicle-Queue/issues/250
> and: https://github.com/OpenHFT/Chronicle-Queue/blob/master/LICENSE%20for%20Open%20Source%20product%20usage.txt
>
> So we are allowed to use the software under the apache license. Is that good enough for us to include Chronicle queues into Aries rsa?
>
> Christian
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: [Discuss] Chronicle Queue transport for Aries rsa (licensing)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Christian,
Chronicle is really interesting. Maybe I would put the RSA Chronicle
part on github (your repo) for now, waiting the "complete" Apache
license switch.
Else as they use dual license, it may not be obvious for "vendor" if
they can use Aries RSA + Chronicle, or not.
My $0.01
Regards
JB
On 03/24/2016 02:42 PM, Christian Schneider wrote:
> I just did a POC Aries rsa transport using Chronicle Queue. It is indeed
> very fast. I get about 500 000 msg/s for one way calls.
> So from a performance perspective I think it would be very interesting
> to have this as a transport.
>
> I am not sure if their licensing works for us though. They have switched
> to lgpl mid last year.
>
> The good news is that I was able to get Peter Lawrey to add a special
> licensing for open source projects like Aries.
> See: https://github.com/OpenHFT/Chronicle-Queue/issues/250
> and:
> https://github.com/OpenHFT/Chronicle-Queue/blob/master/LICENSE%20for%20Open%20Source%20product%20usage.txt
>
>
> So we are allowed to use the software under the apache license. Is that
> good enough for us to include Chronicle queues into Aries rsa?
>
> Christian
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com