Matthieu BRIEDA 264167e3d1 Update Blocklayer to deal with Block1 option ... On the last block answer, the Client still sent another empty message, it didn't take into account the fact that the previous block was sent with m=0. This commit fixed that for me.		2018-03-14 17:24:57 +01:00
..
caching	Porting to Python3	2018-01-23 11:31:46 +01:00
client	set receiver thread as daemon	2018-03-02 15:42:22 +01:00
forward_proxy	removed forced logging	2018-02-21 13:23:47 +01:00
http_proxy	Porting to Python3	2018-01-23 11:31:46 +01:00
layers	Update Blocklayer to deal with Block1 option	2018-03-14 17:24:57 +01:00
messages	Basic client-side implementation of RFC7967: CoAP No-Response Option	2018-02-19 14:06:35 +01:00
resources	Porting to Python3	2018-01-23 11:31:46 +01:00
reverse_proxy	removed forced logging	2018-02-21 13:23:47 +01:00
server	removed forced logging	2018-02-21 13:23:47 +01:00
__init__.py	Porting to Python3	2018-01-23 11:31:46 +01:00
defines.py	Basic client-side implementation of RFC7967: CoAP No-Response Option	2018-02-19 14:06:35 +01:00
serializer.py	Let the outbound payload be binary	2018-03-05 16:41:11 +01:00
serializer.py.bak	Porting to Python3	2018-01-23 11:31:46 +01:00
transaction.py	Porting to Python3	2018-01-23 11:31:46 +01:00
utils.py	Porting to Python3	2018-01-23 11:31:46 +01:00
utils.py.bak	Porting to Python3	2018-01-23 11:31:46 +01:00