You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@bahir.apache.org by "Rosenstark, David" <da...@intel.com> on 2017/07/05 11:01:16 UTC
MQTTUtils
There is an assumption that all data that arrives via MQTT is ASCII. In our case we have a binary payload. If I want to add this functionality, can we change existing functionality or add new one?
---------------------------------------------------------------------
Intel Electronics Ltd.
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
Re: MQTTUtils
Posted by "Rosenstark, David" <da...@intel.com>.
Since the data comes as byte array, it would make sense to leave as is.
From: Luciano Resende <lu...@gmail.com>
Reply-To: "user@bahir.apache.org" <us...@bahir.apache.org>
Date: Thursday, 6 July 2017 at 7:19
To: "user@bahir.apache.org" <us...@bahir.apache.org>
Subject: Re: MQTTUtils
I see two possible options here:
Considering backward compatibility, I believe that having two utility methods would be ok, but this can start making things grow and become hard to maintain and a little inflexible in the long run.
The other option would be to use generics for the key and type of the messages, similar to what is used on Kafka 0.10 streaming connector (e.g. def createDirectStream[K, V] )
Thoughts ?
On Wed, Jul 5, 2017 at 4:01 AM, Rosenstark, David <da...@intel.com>> wrote:
There is an assumption that all data that arrives via MQTT is ASCII. In our case we have a binary payload. If I want to add this functionality, can we change existing functionality or add new one?
---------------------------------------------------------------------
Intel Electronics Ltd.
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
---------------------------------------------------------------------
Intel Electronics Ltd.
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
Re: MQTTUtils
Posted by Luciano Resende <lu...@gmail.com>.
I see two possible options here:
Considering backward compatibility, I believe that having two utility
methods would be ok, but this can start making things grow and become hard
to maintain and a little inflexible in the long run.
The other option would be to use generics for the key and type of the
messages, similar to what is used on Kafka 0.10 streaming connector (e.g.
def createDirectStream[K, V] )
Thoughts ?
On Wed, Jul 5, 2017 at 4:01 AM, Rosenstark, David <
david.rosenstark@intel.com> wrote:
> There is an assumption that all data that arrives via MQTT is ASCII. In
> our case we have a binary payload. If I want to add this functionality, can
> we change existing functionality or add new one?
>
> ---------------------------------------------------------------------
> Intel Electronics Ltd.
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/