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.

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

emq_coap has no response #7

Closed
grutabow opened this issue Dec 1, 2016 · 0 comments
Closed

emq_coap has no response #7

grutabow opened this issue Dec 1, 2016 · 0 comments
Assignees
Labels
Milestone

Comments

@grutabow
Copy link
Contributor

grutabow commented Dec 1, 2016

Environment

OS: linux/win7
Erlang/OTP: R19
EMQ: 2.0
Description

Send a GET request to emq_coap, have no response
Send an OBSERVE request to emq_coap, no response
Mqtt.fx publish a message which a coap client has observed, but this message can not reach the coap client.

@emqplus emqplus added the bug label Dec 1, 2016
@emqplus emqplus added this to the 0.3.0 milestone Dec 1, 2016
grutabow added a commit to grutabow/emq_coap that referenced this issue Dec 1, 2016
1) emq_coap_response: Observe notification replaces ACK with CON.
2) emq_coap_message:serialize_option_list() should return a binary.
3) emq_coap_gateway: Don't use GET to do subscribe because it has no payload
4) emq_coap_gateway:handle_observe() : move topic from payload to Uri-Query
5) emq_coap_channel:handle_response() should handle multiple Uri-Path.
6) emq_coap_app: wrong sequence of prefix and handler.
7) emq_coap.schema: make code more readable.
8) emq_coap.conf: redefine prefix and handler set.
9) README.md: add client code and more information.
emqplus pushed a commit that referenced this issue Dec 5, 2016
@emqplus emqplus modified the milestones: 0.2.7, 0.3.0 Jan 20, 2017
@emqplus emqplus closed this as completed Jan 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants