Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixes for non-blocking with larger payload and improvements to the test and examples #373

Merged
merged 9 commits into from
Nov 28, 2023
Merged

Fixes for non-blocking with larger payload and improvements to the test and examples #373

merged 9 commits into from
Nov 28, 2023

Commits on Nov 22, 2023

  1. Fix for continue during variable part of the header. A continue in th… 

    …e middle of variable would not correctly process for large messages.
    @dgarske
    dgarske committed Nov 22, 2023
    Configuration menu
    Copy the full SHA
    25e27e6 View commit details
    Browse the repository at this point in the history

  2. Further improve WOLFMQTT_TEST_NONBLOCK.

    @dgarske
    dgarske committed Nov 22, 2023
    Configuration menu
    Copy the full SHA
    8e86413 View commit details
    Browse the repository at this point in the history

  3. Fixes for using the -f [file] option with examples. Allow build-tim… 

    …e override of `MAX_BUFFER_SIZE` in examples.
    @dgarske
    dgarske committed Nov 22, 2023
    Configuration menu
    Copy the full SHA
    97cb820 View commit details
    Browse the repository at this point in the history

Commits on Nov 24, 2023

  1. Move the test non-block code into the network callbacks, which know i… 

    …f the non-blocking is allowed.
    @dgarske
    dgarske committed Nov 24, 2023
    Configuration menu
    Copy the full SHA
    dd9973c View commit details
    Browse the repository at this point in the history

Commits on Nov 27, 2023

  1. By default keep mutex locked if we tried to write. The wolfSSL TLS en… 

    …gine requires an SSL_Write that returns WANT_WRITE to be called with the same buffer/sz, not a different one, even if no data was sent. If user wants to enable the feature anyways they can use `WOLFMQTT_ALLOW_NODATA_UNLOCK`. Only the write that has this logic as the issue doesn't exist for an SSL_Read.
    @dgarske
    dgarske committed Nov 27, 2023
    Configuration menu
    Copy the full SHA
    072f5b8 View commit details
    Browse the repository at this point in the history

  2. Add back logic to return MQTT_CODE_CONTINUE if a write lock happens w… 

    …hile data has partially been written.
    @dgarske
    dgarske committed Nov 27, 2023
    Configuration menu
    Copy the full SHA
    6fdcee6 View commit details
    Browse the repository at this point in the history

  3. Improve logic for detection of active read or write. Add test case fo… 

    …r trying to send multiple publishes in the same thread.
    @dgarske
    dgarske committed Nov 27, 2023
    Configuration menu
    Copy the full SHA
    0336347 View commit details
    Browse the repository at this point in the history

  4. Add packet_id to the publish log message in examples.

    @dgarske
    dgarske committed Nov 27, 2023
    Configuration menu
    Copy the full SHA
    8a0cafe View commit details
    Browse the repository at this point in the history

  5. Fixed issue with QoS2 on received publish ACK getting skipped if writ… 

    …e is already locked.
    @dgarske
    dgarske committed Nov 27, 2023
    Configuration menu
    Copy the full SHA
    bc7ae0a View commit details
    Browse the repository at this point in the history