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 thi
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 li
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,
+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
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+Sampl
