Skip to content

Releases: threadly/litesockets

4.14 Release

14 Feb 16:01
Compare
Choose a tag to compare

Fix for MergedByteBuffers modifying the state of the ByteBuffer's provided to them. This was typically seen as a hang or timeout when using SSL, see PR #73 for the details.

release-4.13

09 Dec 19:38
Compare
Choose a tag to compare
Update version to 4.13

4.12 Release

25 Oct 15:53
Compare
Choose a tag to compare

This release includes a bug fix for SimpleMergedByteBuffers to avoid an ArrayOutOfBoundsException. It also includes a threadly upgrade which should provide some performance gains. As well as an internal change to reduce the .slice() operations done to ByteBuffers.

Release 4.11: Threadly upgrade

05 Sep 15:26
Compare
Choose a tag to compare

Upgraded threadly to be safe for internal API deprecations planned for 6.0

4.10 Release for improved stat capabilities

29 May 14:44
Compare
Choose a tag to compare

See PR #67 for the added performance gains of disabling stats, as well as expansions around stats on the SocketExecutor level.

4.9 Bug fix release

03 Dec 15:44
Compare
Choose a tag to compare

Fixes issues where TCP client may not send write (see PR #65 )

4.8 UDP improvements

04 Oct 14:13
55c4aee
Compare
Choose a tag to compare

See PR #64 for details about what has changed in this release

4.7 SSL close notify infinite loop bug fix

21 Aug 21:41
Compare
Choose a tag to compare

Fixes a bug where a remote close or connection downgrade during ssl handshake may result in an infinite loop.

4.6 Release

20 Jun 15:02
abc4505
Compare
Choose a tag to compare

Small improvements to SSLUtils to accept strings instead of just java.io.File

4.5 Bug fix release

15 Jun 21:28
Compare
Choose a tag to compare

Bug fix when using Client.getRead() outside of the client thread. While getRead() should ALWAYS be called from one thread, there is not supposed to be a requirement that it must be on the client thread or from the read listener. This release fixes a possible BufferUnderflowException or a possible NullPointerException that may have been seen if invoked off the client thread.