Hello Roger, On Fri, Jul 27, 2012 at 4:45 PM, Roger Light <ro...@atchoo.org> wrote:
> > I'm not sure how you draw that conclusion. Adding in the sending > client id would require more bandwidth and in most cases you probably > don't care where the message came from. If you do, add it in to the > payload. > I'm not saying that the client ID should be *required* but that it should possible to use this information on the broker side. Thus what I explain below. > > Maybe a workaround would be to have a modified broker which would alter > the > > payload of PUBLISH messages before forwarding them. And that would have > to > > be done inside the broker as the information is only known to it. > > You could of course do this, but it wouldn't be MQTT any more :) > Well, I don't think that would break anything MQTT-wise, but only save some bandwidth between the *first* data producer and its broker. A kind of modifying MQTT proxy. The client id is unique and used to allow persistent/durable clients > (with clean session set to false) to reconnect and recover their > subscriptions and/or queued messages. > [...] > Thanks, that was very helpful -- sorry to ask beginner's questions, I'm quite new to MQTT :-) Regards, -- Damiano ALBANI
-- Mailing list: https://launchpad.net/~mosquitto-users Post to : mosquitto-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~mosquitto-users More help : https://help.launchpad.net/ListHelp
