forked from chrysn/aiocoap
-
Notifications
You must be signed in to change notification settings - Fork 0
/
NEWS
250 lines (197 loc) · 10.4 KB
/
NEWS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
Version 0.4b1
-------------
Tools
~~~~~
* aiocoap-client can now re-format binary output (hex-dumping binary files,
showing CBOR files in JSON-like notation) and apply syntax highlighting. By
default, this is enabled if the output is a terminal. If output redirection
is used, data is passed on as-is.
* aiocoap-fileserver is now provided as a standalone tool. It provides
directory listings in link format, guesses the content format of provided
files, and allows observation.
* aiocoap-rd is now provided as a standalone tool and offers a simple CoRE
Resource Directory server.
Breaking changes
~~~~~~~~~~~~~~~~
* Client observations that have been requested by sending the Observe option
must now be taken up by the client. The warning that was previously shown
when an observation was shut down due to garbage collection can not be
produced easily in this version, and will result in a useless persisting
observation in the background. (See <https://github.com/chrysn/aiocoap/issues/104>)
* Server resources that expect the library to do handle blockwise by returning
true to ``needs_blockwise_assembly`` do not allow random initial access any
more; this this is especially problematic with clients that use a different
source port for every package.
The old behavior was prone to triggering an action twice on non-safe methods,
and generating wrong results in block1+block2 scenarios when a later ``FETCH
block2:2/x/x`` request would be treated as a new operation and return the
result of an empty request body rather than being aligned with an earlier
``FETCH block1:x/x/x`` operation.
* fdc8b024: Support for Python 3.4 is dropped; minimum supported version is now
3.5.2.
* 0124ad0e: The network dumping feature was removed, as it would have been
overly onerous to support it with the new more flexible transports.
* 092cf49f, 89c2a2e0: The content type mapped to the content format 0 was
changed from "text/plain" (which was incorrect as it was just the bare media
type) to the actual content of the IANA registry,
'text/plain;charset="utf8"'. For looking up the content format, text/plain is
is still supported but deprecated.
* 17d1de5a: Handling of the various components of a remote was unified into the
.remote property of messages. If you were previously setting unresolved
addresses or even a tuple-based remote manualy, please set them using the
``uri`` pseudo-option now.
* 47863a29: Re-raise transport specific errors as aiocoap errors as
aiocoap.error.ResolutionError or NetworkError. This allows API users to catch
them independently of the underlying transport.
* f9824eb2: Plain strings as paths in add_resource are rejected. Applications
that did this are very unlikely to have produced the intended behavior, and
if so can be easily fixed by passing in ``tuple(s)`` rather than ``s``.
New features
~~~~~~~~~~~~
* 88f44a5d: TCP and TLS support added; TLS is currently limited to PKI
certificates. This includes support for preserving the URI scheme in
exchanges (0b0214db).
* a50da1a8: The credentials module was added to dispatch DTLS and OSCORE credentials
* f302da07: On the client side, OSCORE can now be used as a transport without
any manual protection steps. It is automatically used for URIs for which a
security context has been registered with the context's client credentials.
* 5e5388ae: Support for PyPy
* 0d09b2eb: NoResponse is now handled automatically. Handlers can override the
default handling by setting a No-Response option on their response
messages, whose value will them be examined by the library to decide whether
the message is actually sent; the No-Response option is stripped from the
outgoing message in the course of that (as it's actually not a response
option).
* b048a50a: Some improvements on multicast handling. There is still no good
support for sending a request to multicast and receiving the individual
responses, but requests to multicast addresses are now unconditionally
handled under the rules of multicast CoAP, even if they're used over the
regular request interface (ie. sending to multicast but processing only the
first response).
* c7ca0286: The software version used to run the server (by default, aiocoap's
version) is now shown in .well-known/core using the impl-info relation.
Deprecations
~~~~~~~~~~~~
* 0d09b2eb: Returning a NoResponse sentinel value is now deprecated.
Assorted changes
~~~~~~~~~~~~~~~~
* Additions to the contrib/ collection of aiocoap based tools:
- widgets, kivy-widgets
- rd-relay
* 95c681a5 and others: Internal interfaces were introduced for the various CoAP
sublayers. This should largely not affect operation (though it does change
the choice of tokens or message IDs); where it does, it's noted above in the
breaking changes.
* 5e5388ae, 9e17180e, 60137bd8: Various fixes to the OSCORE implementation,
which is not considered experimental any more.
* Various additions to the test suite
* 61843d41: Asynchronous ``recvmsg`` calling (as used by the udp6 backend) was
reworked from monkey-patching into using asyncio's ``add_reader`` method, and
should thus now be usable on all asyncio implementations, including uvloop
and gbulb.
* 3ab14c49: .well-known/core filtering will now properly filter by content
format (ct=) in the presence of multiple supported content types.
* 9bd612de: Fix encoding of block size 16.
* 029a8f0e: Don't enforce V4MAPPED addresses in the simple6 backend. This makes
the backend effectively a simple-any backend, as the address family can be
picked arbitrarily by the operating system.
* 8e93eeb9: The simple6 backend now reuses the most recently used 64 sockets.
* cb8743b6: Resolve the name given as binding server name. This enables
creating servers bound exclusively to a link-local address.
* d6aa5f8c: TinyDTLS now pulls in a more recent version of DTLSSocket that has
its version negotiation fixed, and can thus interoperate with recent versions
of libcoap and RIOT's the pending support for DTLS on Gcoap.
* 3d9613ab: Errors in URI encoding were fixed
Version 0.4a1
-------------
Security fixes
~~~~~~~~~~~~~~
* 18ddf8c: Proxy now only creates log files when explicitly requested
* Support for secured protocols added (see Experimental Features)
Experimental features
~~~~~~~~~~~~~~~~~~~~~
* Support for OSCORE (formerly OSCOAP) and CoAP over DTLS was included
These features both lack proper key management so far, which will be
available in a 0.4 release.
* Added implementations of Resource Directory (RD) server and endpoint
* Support for different transports was added. The transport backends to enable
are chosen heuristically depending on operating system and installed modules.
* Transports for platforms not supporting all POSIX operations to run CoAP
correctly were added (simple6, simplesocketserver). This should allow
running aiocoap on Windows, MacOS and using uvloop, but with some
disadvantages (see the the respective transport documentations).
Breaking changes
~~~~~~~~~~~~~~~~
* 8641b5c: Blockwise handling is now available as stand-alone responder.
Applications that previously created a Request object rather than using
Protocol.request now need to create a BlockwiseRequest object.
* 8641b5c: The ``.observation`` property can now always be present in
responses, and applications that previously checked for its presence should
now check whether it is None.
* cdfeaeb: The multicast interface using queuewithend was replaced with
asynchronous iterators
* d168f44: Handling of sub-sites changed, subsites' root resources now need to
reside at path ``("",)``
Deprecations
~~~~~~~~~~~~
* e50e994: Rename UnsupportedMediaType to UnsupportedContentFormat
* 9add964 and others: The ``.remote`` message property is not necessarily a
tuple any more, and has its own interface
* 25cbf54, c67c2c2: Drop support for Python versions < 3.4.4; the required
version will be incremented to 3.5 soon.
Assorted changes
~~~~~~~~~~~~~~~~
* 750d88d: Errors from predefined exceptions like BadRequest("...") are now
sent with their text message in the diagnostic payload
* 3c7635f: Examples modernized
* 97fc5f7: Multicast handling changed (but is still not fully supported)
* 933f2b1: Added support for the No-Response option (RFC7967)
* baa84ee: V4MAPPED addresses are now properly displayed as IPv4 addresses
Tests
~~~~~
* Test suite is now run at Gitlab, and coverage reported
* b2396bf: Test suite probes for usable hostnames for localhost
* b4c5b1d: Allow running tests with a limited set of extras installed
* General improvements on coverage
Version 0.3
-----------
Features
~~~~~~~~
* 4d07615: ICMP errors are handled
* 1b61a29: Accept 'fe80::...%eth0' style addresses
* 3c0120a: Observations provide modern ``async for`` interface
* 4e4ff7c: New demo: file server
* ef2e45e, 991098b, 684ccdd: Messages can be constructed with options,
modified copies can be created with the ``.copy`` method, and default codes
are provided
* 08845f2: Request objects have ``.response_nonraising`` and
``.response_raising`` interfaces for easier error handling
* ab5b88a, c49b5c8: Sites can be nested by adding them to an existing site,
catch-all resources can be created by subclassing PathCapable
Possibly breaking changes
~~~~~~~~~~~~~~~~~~~~~~~~~
* ab5b88a: Site nesting means that server resources do not get their original
Uri-Path any more
* bc76a7c: Location-{Path,Query} were opaque (bytes) objects instead of
strings; disctinction between accidental and intentional opaque options is
now clarified
Small features
~~~~~~~~~~~~~~
* 2bb645e: set_request_uri allows URI parsing without sending Uri-Host
* e6b4839: Take block1.size_exponent as a sizing hint when sending block1 data
* 9eafd41: Allow passing in a loop into context creation
* 9ae5bdf: ObservableResource: Add update_observation_count
* c9f21a6: Stop client-side observations when unused
* dd46682: Drop dependency on obscure built-in IN module
* a18c067: Add numbers from draft-ietf-core-etch-04
* fabcfd5: .well-known/core supports filtering
Internals
~~~~~~~~~
* f968d3a: All low-level networking is now done in aiocoap.transports; it's not
really hotpluggable yet and only UDPv6 (with implicit v4 support) is
implemented, but an extension point for alternative transports.
* bde8c42: recvmsg is used instead of recvfrom, requiring some asyncio hacks
Package management
~~~~~~~~~~~~~~~~~~
* 01f7232, 0a9d03c: aiocoap-client and -proxy are entry points
* 0e4389c: Establish an extra requirement for LinkHeader