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 <[email protected]> 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 <[email protected]> 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 <http://wso2.com>* >> cell: +94 77 7779495 >> > > > > -- > Ramith Jayasinghe > Technical Lead > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > E: [email protected] > P: +94 772534930 > -- *Pamod Sylvester * *WSO2 Inc.; http://wso2.com <http://wso2.com>* cell: +94 77 7779495
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
