[dispatch-router] 1.16.0 release content

[Chuck Rolke <cr...@redhat.com>]

This note is about the qpid-dispatch 1.16 content and features.
The schedule discussion is separate in a thread titled "[dispatch-router] 1.16.0 release schedule".

This note summarizes 

TCP Adaptor
-----------

* DISPATCH-1968 fixed a memory corruption/crash issue.
  See https://issues.apache.org/jira/browse/DISPATCH-1968
  Without this fix the router misbehaves.

* The TCP Adaptor is not using input flow control.
  See https://issues.apache.org/jira/browse/DISPATCH-1947
  This code must include the logic for HTTP1 in https://github.com/apache/qpid-dispatch/pull/1039 .
  Without flow control the TCP Adaptor receives input without bound and may consume lots of memory.

* TCP Adaptor uses 512-byte buffers for Proton I/O. 
  See https://issues.apache.org/jira/browse/DISPATCH-1975
  Larger Proton buffers would improve input and output performance, lower CPU usage,
  and have fewer Proton events to handle.
  Without changing buffer sizes the adaptor works fine but runs more slowly than it could.

* TCP Adaptor leaks resources when server-side connection closes first.
  See https://issues.apache.org/jira/browse/DISPATCH-1972
  For many cases there are no leaks but fixing leaks is always good.
  Without change the current code may leak many buffers, especially if there is no flow control.

* TCP Adaptor (and HTTP adaptors) are not integrated with policy connection count.
  See https://issues.apache.org/jira/browse/DISPATCH-1967
  Without change the router does not honor the global connection limit set by policy.

* Adaptors and Proton need to support half-closed TCP connections.
  See https://issues.apache.org/jira/browse/DISPATCH-1878
  This change involves coordination with Proton to support read and write close over raw connections.
  Without this change applications that close the sending connection "too soon" may not receive a response.

I would like to see issues 1968, 1947, and 1975 prioritized for the next release.
The other issues may be deferred if necessary.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org