awslabs / aws-c-mqtt

C99 implementation of the MQTT 3.1.1 specification.
Apache License 2.0
93 stars 29 forks source link

Update README to accurately reflect what is copied #359

Closed Octogonapus closed 7 months ago

Octogonapus commented 8 months ago

The README was not updated when changes were made to copy parameters such as the topic filter and payload for various functions. This PR fixes those instances so that the documentation is accurate.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

bretambrose commented 8 months ago

Honestly, most of that README should be removed. We don't want people using the 311 implementation and this is not a stable API in general.

Octogonapus commented 8 months ago

Why don't you want people using the v3.1.1 implementation? The AWS broker still supports v3.1.1. Is it being phased out in favor of the v5 to v3.1.1 adapter?

bretambrose commented 8 months ago

Why don't you want people using the v3.1.1 implementation? The AWS broker still supports v3.1.1. Is it being phased out in favor of the v5 to v3.1.1 adapter?

Nothing's being phased out at the moment.

The 311 implementation was the first client that got written on top of the CRT event loop APIs. As such it has a lot of properties/decisions that we've come to regret.

In my ideal world, everyone would use the 5 client. It's not perfect (as I work on another rust MQTT client as a personal project, I keep finding small things that could be improved) but it is much more maintainable and easy to reason about. Maybe someday we can extend the current 5 client to also have a 311 mode while keeping the current API contract and sunset the 311 implementation, but that's just a pipe dream atm.

Octogonapus commented 8 months ago

Thank you for explaining that!