|Re: [paho-dev] what's the purpose of WILLTOPICUPD, WILLMSGUPD ?|
yes, for this sort of transparent gateway, WILLTOPICUPD and WILLMSGUPD do not make much sense. The only option I can think of is that the gateway stored that information for the next connect, but I don't think that's something we want to do.
For an aggregating gateway, like RSMB, it would make sense, because the firing of the will message is the responsiblity of the gateway.
For your implementation, I think it's fine for the gateway to return a not supported return code (0x03) for WILLTOPICUPD and WILLMSGUPD.
On 04/06/2016 08:43 AM, Tomoaki Yamaguchi wrote:
and Encapsulated message.tomoakiwelcome any comments.In what situation we need those messages?I don't know G/W should keep Will topic and Will Message or not.But, I have no idea how G/W handles WILLTOPICUPD and WILLMSGUPD.Hi,I almost done the coding of MQTT-SN gateway and start debugging now on.
Those seem use less for G/W. MQTT protocol dose not have those messages.if the client wants update those, it's enough to reconnect with updated will topic or will message.
At this point G/W does not support WILlTOPICUPD, WILLMSGUPD, WILLTOPICRESP, WILLMESGRESP,
_______________________________________________ paho-dev mailing list paho-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/paho-dev
_______________________________________________-- Ian Craggs icraggs@xxxxxxxxxx IBM United Kingdom Paho Project Lead; Committer on Mosquitto
paho-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top