Giters
tpitale
/
coap_ex
CoAP Server/Client with support for Phoenix
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
16
Watchers:
6
Issues:
39
Forks:
2
tpitale/coap_ex Issues
Plug.Conn.req_headers
Updated
3 years ago
content_type vs content_format
Updated
3 years ago
License
Closed
3 years ago
Comments count
2
Split Messaging/Application layers
Updated
3 years ago
Comments count
1
[refactor] Move Connection.start_handler and start_socket_for to CoAP
Updated
3 years ago
Comments count
2
Connection: check if the message_id matches what we may have already sent?
Updated
3 years ago
Comments count
1
[ci] Use circleci
Closed
3 years ago
Comments count
1
[test] Multipart.as_blocks
Updated
3 years ago
[test] Multipart.build
Updated
3 years ago
[test] test Payload next_segment with StreamData
Updated
3 years ago
Conenction: handle exponential backoff timeout
Updated
3 years ago
Connection: handle connection timeout
Updated
3 years ago
Multipart struct: redefine as description/control based on request/response
Updated
3 years ago
Payload: split into the appropriate segment
Updated
3 years ago
Phoenix.Request: use struct ?
Updated
3 years ago
MessageOptions: ensure decoding size
Updated
3 years ago
Comments count
1
mesage_options: add struct ?
Updated
3 years ago
conn.ex: options for filtered headers
Updated
3 years ago
Add support for coaps ?
Updated
3 years ago
[refactor] socket_server: move start_connection
Updated
3 years ago
[improvement] in server-socket
Updated
3 years ago
[improvement] leverage handle_continue in `init/1`
Updated
3 years ago
Struct spec: errorneous CoAP.Message
Closed
4 years ago
When acting as a server, timeout occurs after a block transfer completes
Closed
4 years ago
Crash when a response is received and connection is missing
Closed
4 years ago
Comments count
1
Long timeout after final retry
Closed
5 years ago
Retries should be reset when receiving a message from peer
Closed
5 years ago
Comments count
1
Add telemetry for tracking
Closed
5 years ago
Comments count
1
Reset retries when get a packet
Closed
5 years ago
Comments count
1
Ensure we cancel timers when we get any packet
Closed
5 years ago
Comments count
1
Close socket after client connection is done
Closed
5 years ago
Send reset message when receiving a response and no connection exists
Updated
5 years ago
Add exchange timeouts
Updated
5 years ago
Repeat request when ack received with no payload
Updated
5 years ago
Handle late :ack
Updated
5 years ago
Crash if client connection receives data after timeout
Closed
5 years ago
Comments count
3
Set defaults for connection handling as per spec
Closed
5 years ago
Comments count
3
Track message_ids used on a connection
Updated
5 years ago
Comments count
1
Empty blocks should not result in option being present in request/response
Closed
5 years ago