Skip to content

ESP-NOW documentation and updating Coap documentation after esp-idf 4.1 update #292

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.

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

Closed
wants to merge 9 commits into from

Conversation

geza-pycom
Copy link
Contributor

No description provided.

Copy link
Contributor Author

@geza-pycom geza-pycom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check my comments.

@geza-pycom
Copy link
Contributor Author

geza-pycom commented Jan 22, 2021

@peter-pycom : just heads up that please do not merge this once we have discussed all the comments, I am not sure whether this is the correct branch to merge these updates.

@geza-pycom geza-pycom changed the title Updating Coap documentation after esp-idf 4 update ESP-NOW documentation and updating Coap documentation after esp-idf 4.1 update Jan 22, 2021
peter-pycom
peter-pycom previously approved these changes Feb 10, 2021
Copy link
Contributor

@peter-pycom peter-pycom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice. It's much clearer to me now. Thanks.

@@ -158,13 +160,14 @@ Registers a callback function which will be called when a new resource has been
* `callback` is the callback to be registered. The callback must have 1 argument:
* `resource` is the new resource which has been created

#### Coap.new_client_session(destination, port=5683, protocol=UDP)
#### Coap.new_client_session(address, *, port=5683, psk=None, identity=None)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

new_client_session() has lost the protocol param, but remove_client_session() still has it. intentional?

Copy link
Contributor Author

@geza-pycom geza-pycom Feb 10, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it is.
When you call new_client_session() the Protocol is figured out based on the PSK and Identity parameters.
When you cal remove_client_session() it may happen that you have 2 Clients connected to the same Port, but one is using UDP the other is DTLS.

@peter-pycom
Copy link
Contributor

I think you guys agreed on a branch for this, right? Can you update the PR?

@geza-pycom
Copy link
Contributor Author

New request opened towards correct branch: #387

@geza-pycom geza-pycom closed this Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants