Releases: Musixal/Backhaul
Releases · Musixal/Backhaul
v0.5.0
Changelog
- 7a30fef Increase TCP read/write buffer memory for better UDP support
- 0675482 Feat: Add workers based on CPU threads
- abff19f Fix: add new signal func for udp support
- e41897e add accept_udp options to server side
- b744a8f Feat: Fully support UDP over TCP with congestion control
- 1852cac minor log and channelHandler enhancement
v0.4.5
v0.4.4
Changelog
- 7f96e7b Introduce 1ms delay after opening SMUX stream to prevent header misinterpretation in WebSocket mode
- e1d6bf6 increase channel handler capacity
- 04f4526 Apply temporary TCP optimizations for Linux to handle massive connections
- ab229e0 change default dial timeout to 10 seconds
- ccdd40b Implement retry logic for TCP/WS dialer to mitigate timeouts
- 79de2dd fix: close connection after failed handshake
- 0585927 fix: server-side panic by ensuring valid tunnel connections before proceeding with data exchange.
- 096f522 fix: mux transport better error handling
v0.4.3
v0.4.2
v0.4.1
v0.4.0
Changelog
- [Feat] Refactored MUX Transports.
- [Feat] Hot-Reloadable Configuration. Added support for hot-reloading the configuration file, allowing dynamic updates without restarting the application.
- Performance improvements across all transpors.
- Use io.copy for better performance.
- TCP control channel enhacement.
Breaking Changes
This update introduces breaking changes for MUX Transports and is not backward compatible with previous versions:
mux_sessionRemoved,mux_conApplied to Server.- The
mux_sessionoption has been deprecated. You must now specifymux_con(MUX concurrency) for the server configuration.
- The
channel_sizeandheartbeatApplied to Serverconnection_poolApplied to Client- Performance Boost: These changes result in a significant performance upgrade, especially in high-concurrency scenarios.
Let me know if further improvements are needed!
v0.3.3
Changelog
- Removal of Windows operating system support
- [feat] Add SO_REUSEPORT and SO_REUSEADDR socket option to WS and TCP
- [fix] Transferring pool connection management from server to client
- Remove the port forwarder
- [feat] New format of the port section
- Changing the default values of some options
Breaking Changes
- ُThe connection pool must be defined in the client section.
- The forwarder section has been removed and you can specify the remote ip address instead of it in the ports section.
v0.3.2
Changelog
- [fix] tcp/ws optimization
- [feat] add workers for tcp tunnel listener
- [fix] TCP_NODELAY
v0.3.1
Changelog
- 597e51b bump version to v0.3.1
- [fix] ws and tcp channel stability
- [fix] fix restart issue for all transports
- [fix] tcp stability