Skip to content

0.7.0

Latest
Compare
Choose a tag to compare
@Johnnei Johnnei released this 08 Nov 16:01
· 13 commits to develop since this release
0.7.0
12e8942

Added

  • JBT-104: NioPeerConnector is now available. This connector is optimized to run with out a dedicated thread but on
    the executor threads.
  • JBT-110: TorrentClientSettings is introduced on TorrentClient to separate client state from configuration

Changed

  • JBT-98: The network layer has been rewritten to be event driven in favor of polling.
  • JBT-100: AbstractPeerConnectionAcceptor has been replaced by BitTorrentHandshakeHandler
  • JBT-102: ISocket has been remodelled around Channels instead of Sockets.
  • JBT-104: BitTorrentSocket is now always a socket which has passed the handshake process.
  • JBT-99: Peer IO is now processed until it can no longer be executed without blocking.
  • JBT-106: Unsupported tracker protocols no longer throw an exception but will log a warning and return Optional#empty
  • JBT-107: UDP Trackers now support the common /announce suffix.
  • JBT-116: Connection queue has been given a priority strategy to (mostly) evenly split over torrents.
  • JBT-117: Peer#addBlockRequest now rejects when the peer is choked
  • JBT-117: Metadata phases now use a dedicated choking strategy to show interest into clients which have the metadata and the ut_metadata extension data
  • JBT-110: UtpModule now reuses the download port set on the TorrentClient

Deprecated

  • JBT-102: Peer#getBitTorrentSocket() is now deprecated. The BitTorrentSocket will become an internal class.
    Functionality will be replaced.
  • JBT-110: UtpModule.Builder#listenOn(int) now reuses the download port set on the TorrentClient

Fixed

  • JBT-110: Remote connections coming in through uTP now correctly get ignored when isAcceptingConnections is false.

Removed

  • JBT-102: BitTorrentSocket has forgotten how to process handshakes.