Re: [Dev] Option to ship MQTT client lib with ESB

[Pamod Sylvester]

Hi Isuru,

I agree with your point in having the challenge to maintain with client
upgrades.

Just saw the MQTT client library in the angle of other transport libraries
we ship currently i.e HttpCore.

Thanks,
Pamod

On Wed, Jun 8, 2016 at 2:47 PM, Isuru Udana  wrote:

> Hi Pamod, Ramith,
>
> I think we should try to de-couple our component from external libs as
> much as we can. If we do this even for a minor version upgrade either we
> have wait until the next release or else we need to patch the server. In
> the current approach it is just a matter of dropping the new library.
> If we don't have direct code level dependancies to a particular library,
> IMO we should not pack it.
>
> Thanks.
>
>
> On Wed, Jun 8, 2016 at 1:39 PM, Pamod Sylvester  wrote:
>
>> Hi Ramith,
>>
>> Yes. That's something to think about.
>>
>> AFAIK currently there's no explicit way to handle the library upgrades.
>> Unless the upgrade includes with either a new ESB release or a patch.
>>
>> Since the client library generic and is tested for interoperability for a
>> given version of MQTT protocol, AFAIU the chance would be less for client
>> library to require a mandatory upgrade for each broker release, unless the
>> broker changes the supporting protocol version.
>>
>> Thanks,
>> Pamod
>>
>> On Wed, Jun 8, 2016 at 12:27 PM, Ramith Jayasinghe 
>> wrote:
>>
>>> +1. that's a good idea. BTW, how are we going to handle version upgrades
>>> (for client lib) ?
>>>
>>> On Wed, Jun 8, 2016 at 7:19 AM, Pamod Sylvester  wrote:
>>>
 Hi All,

 Could we consider the $Subject, (since the library is interoperable
 with all standard MQTT brokers).

 Currently it requires client lib to be separately downloaded when
 integrating with a broker [1]

 [1]
 https://docs.wso2.com/display/ESB490/Sample+906%3A+Inbound+Endpoint+MQTT+Protocol+Sample

 Thanks,
 Pamod

 --
 *Pamod Sylvester *

 *WSO2 Inc.; http://wso2.com *
 cell: +94 77 7779495

>>>
>>>
>>>
>>> --
>>> Ramith Jayasinghe
>>> Technical Lead
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> E: ram...@wso2.com
>>> P: +94 772534930
>>>
>>
>>
>>
>> --
>> *Pamod Sylvester *
>>
>> *WSO2 Inc.; http://wso2.com *
>> cell: +94 77 7779495
>>
>
>
>
> --
> *Isuru Udana*
> Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>



-- 
*Pamod Sylvester *

*WSO2 Inc.; http://wso2.com *
cell: +94 77 7779495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Option to ship MQTT client lib with ESB

[Isuru Udana]

Hi Pamod, Ramith,

I think we should try to de-couple our component from external libs as much
as we can. If we do this even for a minor version upgrade either we have
wait until the next release or else we need to patch the server. In the
current approach it is just a matter of dropping the new library.
If we don't have direct code level dependancies to a particular library,
IMO we should not pack it.

Thanks.


On Wed, Jun 8, 2016 at 1:39 PM, Pamod Sylvester  wrote:

> Hi Ramith,
>
> Yes. That's something to think about.
>
> AFAIK currently there's no explicit way to handle the library upgrades.
> Unless the upgrade includes with either a new ESB release or a patch.
>
> Since the client library generic and is tested for interoperability for a
> given version of MQTT protocol, AFAIU the chance would be less for client
> library to require a mandatory upgrade for each broker release, unless the
> broker changes the supporting protocol version.
>
> Thanks,
> Pamod
>
> On Wed, Jun 8, 2016 at 12:27 PM, Ramith Jayasinghe 
> wrote:
>
>> +1. that's a good idea. BTW, how are we going to handle version upgrades
>> (for client lib) ?
>>
>> On Wed, Jun 8, 2016 at 7:19 AM, Pamod Sylvester  wrote:
>>
>>> Hi All,
>>>
>>> Could we consider the $Subject, (since the library is interoperable with
>>> all standard MQTT brokers).
>>>
>>> Currently it requires client lib to be separately downloaded when
>>> integrating with a broker [1]
>>>
>>> [1]
>>> https://docs.wso2.com/display/ESB490/Sample+906%3A+Inbound+Endpoint+MQTT+Protocol+Sample
>>>
>>> Thanks,
>>> Pamod
>>>
>>> --
>>> *Pamod Sylvester *
>>>
>>> *WSO2 Inc.; http://wso2.com *
>>> cell: +94 77 7779495
>>>
>>
>>
>>
>> --
>> Ramith Jayasinghe
>> Technical Lead
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> E: ram...@wso2.com
>> P: +94 772534930
>>
>
>
>
> --
> *Pamod Sylvester *
>
> *WSO2 Inc.; http://wso2.com *
> cell: +94 77 7779495
>



-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Option to ship MQTT client lib with ESB

[Pamod Sylvester]

Hi Ramith,

Yes. That's something to think about.

AFAIK currently there's no explicit way to handle the library upgrades.
Unless the upgrade includes with either a new ESB release or a patch.

Since the client library generic and is tested for interoperability for a
given version of MQTT protocol, AFAIU the chance would be less for client
library to require a mandatory upgrade for each broker release, unless the
broker changes the supporting protocol version.

Thanks,
Pamod

On Wed, Jun 8, 2016 at 12:27 PM, Ramith Jayasinghe  wrote:

> +1. that's a good idea. BTW, how are we going to handle version upgrades
> (for client lib) ?
>
> On Wed, Jun 8, 2016 at 7:19 AM, Pamod Sylvester  wrote:
>
>> Hi All,
>>
>> Could we consider the $Subject, (since the library is interoperable with
>> all standard MQTT brokers).
>>
>> Currently it requires client lib to be separately downloaded when
>> integrating with a broker [1]
>>
>> [1]
>> https://docs.wso2.com/display/ESB490/Sample+906%3A+Inbound+Endpoint+MQTT+Protocol+Sample
>>
>> Thanks,
>> Pamod
>>
>> --
>> *Pamod Sylvester *
>>
>> *WSO2 Inc.; http://wso2.com *
>> cell: +94 77 7779495
>>
>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 772534930
>



-- 
*Pamod Sylvester *

*WSO2 Inc.; http://wso2.com *
cell: +94 77 7779495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Option to ship MQTT client lib with ESB

[Ramith Jayasinghe]

+1. that's a good idea. BTW, how are we going to handle version upgrades
(for client lib) ?

On Wed, Jun 8, 2016 at 7:19 AM, Pamod Sylvester  wrote:

> Hi All,
>
> Could we consider the $Subject, (since the library is interoperable with
> all standard MQTT brokers).
>
> Currently it requires client lib to be separately downloaded when
> integrating with a broker [1]
>
> [1]
> https://docs.wso2.com/display/ESB490/Sample+906%3A+Inbound+Endpoint+MQTT+Protocol+Sample
>
> Thanks,
> Pamod
>
> --
> *Pamod Sylvester *
>
> *WSO2 Inc.; http://wso2.com *
> cell: +94 77 7779495
>



-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 772534930
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Option to ship MQTT client lib with ESB

[Pamod Sylvester]

Hi All,

Could we consider the $Subject, (since the library is interoperable with
all standard MQTT brokers).

Currently it requires client lib to be separately downloaded when
integrating with a broker [1]

[1]
https://docs.wso2.com/display/ESB490/Sample+906%3A+Inbound+Endpoint+MQTT+Protocol+Sample

Thanks,
Pamod

-- 
*Pamod Sylvester *

*WSO2 Inc.; http://wso2.com *
cell: +94 77 7779495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev