Point out different handling of MQTT # wildcard in the "Differences from MQTT" section

[jurijsteblaj]

Hi,

I think it would be appropriate to point out that AWS IoT handles # differently than the specification linked in the section AWS IoT differences from MQTT version 3.1.1 specification.

The MQTT v3.1.1 specification specifies "The multi-level wildcard represents the parent and any number of child levels." The topic filter "sport/#" should match the topic "sport". That is not the case with AWS IoT which does not match the parent topic.

While the way AWS IoT handles # is documented in Topic filters I think this difference from specification is worth mentioning in a bullet point in the "Differences from MQTT" section.

I would be willing to write this addition and make a PR if you give me the go-ahead.

[gausekha]

Hi,

Thank you for the feedback and for helping us improve the developer guide documentation. I have added a bullet point in the AWS IoT differences from MQTT version 3.1.1 specification section of the page. Feel free to review this addition to the page and please let us know if you have any questions.

Thanks!
Gautham

[jurijsteblaj]

That's great. Thanks!

Best regards
Jurij