[Logo] The Limax project
  [Search] 搜索   [Recent Topics] 最新主题   [Hottest Topics] 热门主题   [Members]  会员列表   [Groups] 返回首页 
[Register] 会员注册 / 
[Login] 登入 
The latest version limax-5.16-b4613(release on 2019/05/22)  XML
论坛首页 » 系统公告
发表人 内容

注册时间: 02/09/2015 15:53:01
文章: 52

Current version:5.16-b4613
Release date: 2019/05/22

limax-5.16-b4613 (2019/05/22)
1. Add the createAlarm method for limax.io.net.NetTask to allow more Alarm timers to be created for the current nettask.
2. Change the priority and the implementation of flow control of HTTP/2. The egress mode is changed to ingress mode. At the same time, similar to HTTP/1.1, the request is processed in units of connections, which ultimately reduces the server memory overhead. Add the flow control window parameters consistent with HTTP/1.1. (The egress method relies on the peer window announcement to try the best efforts to fill the send buffer. Combined with the use of memory mapping, it can achieve very good performance when dealing with large files. File data will not enter user space at all, and there is no substantial heap requirement for large data block transmissions.. However, when HTTP/2 runs in TLS mode, multiple users access the same file, and the file data will be encrypted into multiple different versions, generating a large number of heap requirements, so the advantages of memory mapping no longer exist. The result is that in TLS mode, it is impossible to prevent malicious clients from notifying huge windows and accessing huge files to cause memory overflow.)
3. Unify the alarm behavior of WebSocket in HTTP/1.1 and RFC8441 two modes.
4. Add the congestion timeout configuration, constrain the sending behavior in all modes, and close the connection as soon as the congestion times out.
5. Adjust the limax.http.HttpHandler interface, replace the postLimit method with the censor method, and support more flexible and controllable upload review.
6. Add a cancel method for limax.http.Exchange that allows the server to terminate the network connection as soon as it detects malicious behavior.
7. The release time of the Server-Sent Events object is clarified by the onClose message. (Whether it is a network accident, or actively perform done method, the onClose guarantees to schedule only once).
8. Change limax.http.HttpExchange.async(DataSupplier) to limax.http.HttpExchange.async(HttpHandler handler) for better conceptual consistency.
9. Update relative manuals and examples.
论坛首页 » 系统公告
Powered by JForum 2.1.9 © JForum Team