Update RELEASE_NOTES.md and CHANGES.md
This commit is contained in:
@@ -16,8 +16,13 @@ This file is a best-effort approach to solving this issue; we will do our best b
|
||||
|
||||
### New API
|
||||
|
||||
* (applications) Added two new base classes for source and sink applications, `SourceApplication` and `SinkApplication`, respectively.
|
||||
|
||||
### Changes to existing API
|
||||
|
||||
* (applications) Deprecated attributes `RemoteAddress` and `RemotePort` in UdpClient, UdpTraceClient and UdpEchoClient. They have been combined into a single `Remote` attribute.
|
||||
* (applications) Deprecated attributes `ThreeGppHttpClient::RemoteServerAddress` and `ThreeGppHttpClient::RemoteServerPort`. They have been combined into a single `ThreeGppHttpClient::Remote` attribute.
|
||||
|
||||
### Changes to build system
|
||||
|
||||
### Changed behavior
|
||||
|
||||
@@ -32,6 +32,11 @@ The required Doxygen version for documentation generation is version 1.11.
|
||||
|
||||
### New user-visible features
|
||||
|
||||
- (applications) - Attributes `RemoteAddress` and `RemotePort` in UdpClient, UdpTraceClient and UdpEchoClient have been combined into a single `Remote` attribute. Similarly, the `ThreeGppHttpClient::RemoteServerAddress` and `ThreeGppHttpClient::RemoteServerPort` attributes have been combined into a single `ThreeGppHttpClient::Remote` attribute. The constructors of corresponding helper classes have been changed to make use of these new attributes.
|
||||
- (applications) - The `ThreeGppHttpServer::LocalAddress` and `ThreeGppHttpServer::LocalPort` attributes have been renamed to `ThreeGppHttpServer::Remote` and `ThreeGppHttpServer::Port`, respectively.
|
||||
- (applications) - It is now possible to specify the address on which to bind the listening socket for UdpServer via the `Local` attribute.
|
||||
- (applications) - It is now possible to specify a port only for PacketSink to listen to any address (both IPv4 and IPv6).
|
||||
|
||||
### Bugs fixed
|
||||
|
||||
## Release 3.43
|
||||
|
||||
Reference in New Issue
Block a user