All Classes and Interfaces
Class
Description
IP address abstraction supporting both IPv4 and IPv6 formats.
This alert is always posted when a torrent was attempted to be added
and contains the return status of the add operation.
Configuration parameters for adding a torrent to the session.
Callback interface for receiving notifications from the bittorrent session.
This alert is posted to indicate to the client that some alerts were
dropped.
Announces are sent to each tracker using every listen socket, this class
holds information about one listen socket for one tracker.
Metadata for a single tracker in a torrent's announce list.
Announcement status for a specific info-hash at a tracker endpoint.
Parser and wrapper for bencoded data structures (BitTorrent metadata format).
This alert is generated when a block request is sent to a peer.
This alert is generated when a block request receives a response.
Download progress and state information for a single block within a piece.
This is the enum used for .
This alert is generated when a block request times out.
This alert is posted when a block intended to be sent to a peer is placed in the
send buffer.
This alert is posted when the disk cache has been flushed for a specific
torrent as a result of a call to torrent_handle::flush_cache().
These are all the reasons to disconnect a peer
all reasons caused by the peer sending unexpected data.
This alert is generated when a DHT node announces to an info-hash on our
DHT node.
This alert is posted when the initial DHT bootstrap is done.
This is posted exactly once for every call to
SessionHandle.dhtDirectRequest(UdpEndpoint, Entry, long).Posted when something fails in the DHT.
This alert is generated when a DHT node sends a ``get_peers`` message to
our DHT node.
This alert is posted as a response to a call to
SessionHandle.dhtGetItem(Sha1Hash),
looking up immutable items in the DHT.Statistics for an active Distributed Hash Table (DHT) lookup operation.
This alert is posted as a response to a call to session::get_item(),
specifically the overload for looking up mutable items in the DHT.
This alert is generated when we send a get_peers request.
This alert is posted every time a DHT message is sent or received.
This is posted when a DHT put operation completes.
This alert is generated each time the DHT receives peers from a node.
Statistics for a single bucket in the DHT routing table.
Contains current DHT state.
Ed25519 elliptic curve cryptography for DHT and security operations.
Variant container for bencoded data structures.
Utilities for enumerating network interfaces and routing tables on the local system.
Network interface information including address, netmask, and interface name.
Network routing table entry describing a route to a destination network.
Error status information from libtorrent operations.
Whenever libtorrent learns about the machines external IP, this alert is
generated.
This alert is generated when a fastresume file has been passed
to
addTorrent but the files on disk did not match the
fastresume file.This is posted whenever an individual file completes its download.
If the storage fails to read or write files that it needs access
to, this alert is generated and the torrent is paused.
Posted when a or
update of the file
priorities complete, which requires a round-trip to the disk
thread.
This is posted as a response to a
TorrentHandle.renameFile(int, String), if the rename
operation succeeds.This is posted as a response to a torrent_handle::rename_file() call, if the rename
operation failed.
Represents a window of a file in a torrent.
Represents the file structure and piece mapping for a torrent.
This alert is generated when a finished piece fails its hash check.
this alert is used to report errors in the i2p SAM connection.
The incoming connection alert is posted every time we successfully accept
an incoming connection, through any mean.
Posted every time an incoming request from a peer is accepted and queued
up for being serviced.
Dual-hash support for BitTorrent v1 (SHA-1) and v2 (SHA-256) torrents.
Circular buffer for storing time-series integer statistics.
This is a debug alert that is generated by an incoming invalid piece request.
System information and version utilities for libtorrent and jlibtorrent.
This alert is generated when none of the ports, given in the port range, to
session can be opened for listening.
This alert is posted when the listen port succeeds to be opened on a
particular interface.
This alert is posted by some session wide event.
Posted if the local service discovery socket fails to start properly.
This alert is generated when we receive a local service discovery message
from a peer for a torrent we're currently participating in.
This alert is generated when the metadata has been completely received and the info-hash
failed to match it.
This alert is generated when the metadata has been completely received and the torrent
can start downloading.
Flags controlling storage move behavior for torrent files.
Identifies the type of operation that caused an error or peer disconnect.
This alert may be posted when the initial checking of resume data and files
on disk (just existence, not piece hashes) completes.
Generic pair container for holding two related values of different types.
Summary statistics for an incomplete piece with ongoing block transfers.
The peer alert is a base class for alerts that refer to a specific peer.
This alert is generated when a peer is banned because it has sent too many corrupt pieces
to us.
This alert is posted when an incoming peer connection, or a peer that's about to be added
to our peer list, is blocked for some reason.
This alert is posted every time an outgoing peer connect attempts succeeds.
This alert is generated when a peer is disconnected for any
reason (other than the ones covered by ).
This alert is generated when a peer sends invalid data over the
peer-peer protocol.
Statistics and information for a single connected peer.
The kind of connection this is.
posted when torrent_handle::post_peer_info() is called.
This alert is posted by events specific to a peer.
Describes whether this log refers to in-flow or out-flow of the
peer.
Represents a byte range request within a piece in the BitTorrent protocol.
This alert is generated when a peer is snubbed, when it stops sending data when we request
it.
This alert is generated when a peer is unsnubbed.
This alert is generated when a limit is reached that might have a negative impact on
upload or download rate performance.
This is posted when one or more blocks are picked by the piece picker,
assuming the verbose piece picker logging is enabled (see
picker_log_notification).
This alert is posted every time a piece completes downloading
and passes the hash check.
The bitfield type stores any number of bits as a bitfield
in a heap allocated array.
posted when torrent_handle::post_download_queue() is called
Tracks download completion status for files and pieces in a torrent.
This alert is generated when a NAT router was successfully found and
a port was successfully mapped on it.
This alert is generated when a NAT router was successfully found but some
part of the port mapping request failed.
This alert is generated to log informational events related to either
UPnP or NAT-PMP.
Protocol for port mapping with UPnP and NAT-PMP.
Transport protocol for automatic port mapping on home routers.
Priority levels for downloading pieces and files in a torrent.
This alert is posted when the asynchronous read operation initiated by
a call to
TorrentHandle.readPiece(int)
is completed.This alert is generated when a peer rejects or ignores a piece request.
This alert is generated as a response to a ``torrent_handle::save_resume_data`` request.
This alert is generated instead of ``save_resume_data_alert`` if there was an error
generating the resume data.
If a scrape request fails, this alert is generated.
This alert is generated when a scrape request succeeds.
This alert is posted when the session encounters a serious error,
potentially fatal.
The session holds all state that spans multiple torrents.
Central orchestrator for all bittorrent session operations in jlibtorrent.
Mutable DHT item with signature and sequence number.
Configuration parameters for initializing a bittorrent session.
Aggregated session-wide statistics with sliding average tracking.
The is posted when the user requests session
statistics by calling
SessionHandle.postSessionStats()
on the session object.The session_stats_header alert is posted during the init of the
session thread.
The ``settings_pack`` struct, contains the names of all settings as
enum values.
Immutable 20-byte SHA-1 hash wrapper.
Immutable 32-byte SHA-256 hash wrapper for BitTorrent v2 torrents.
This alert is posted with SOCKS5 related errors when a SOCKS5 proxy is
configured.
Generated whenever a torrent changes its state.
This alert is only posted when requested by the user, by calling
SessionHandle.postTorrentUpdates().Metadata describing a single session statistic metric.
Disk storage allocation strategy for torrents.
This alert is generated when all the disk IO has completed and the
files have been moved, as an effect of a call to
TorrentHandle.moveStorage(java.lang.String, com.frostwire.jlibtorrent.MoveFlags).This alert is generated when an attempt to move the storage,
via
TorrentHandle#moveStorage fails.A network address and TCP port pair for peer connections in BitTorrent.
This is a base class for alerts that are associated with a
specific torrent.
Fluent builder for creating .torrent files from local files and directories.
Callback interface for torrent creation events.
Result of torrent creation containing metadata and bencoded data.
This alert is posted when a torrent completes checking.
This alert is posted when two separate torrents (magnet links) resolve to
the same torrent, thus causing the same torrent being added twice.
This alert is generated when a request to delete the files of a torrent complete.
This alert is generated when a request to delete the files of a torrent fails.
This is posted whenever a torrent is transitioned into the error state.
This alert is generated when a torrent switches from being a downloader to a seed.
Flags controlling torrent startup behavior and operating modes.
Handle to a torrent currently active in the session.
Represents the metadata contained in a .torrent file or magnet link.
This alert is posted by torrent wide events.
This is always posted for SSL torrents.
This alert is generated as a response to a ``torrent_handle::pause`` request.
The ``torrent_removed_alert`` is posted whenever a torrent is removed.
This alert is generated as a response to a torrent_handle::resume() request.
To be used in concert with .
Time-series metrics available in
TorrentStats.Real-time snapshot of a torrent's status and statistics.
the different overall states a torrent can be in.
This is a base class used for alerts that are associated with a
specific tracker.
This alert is generated each time a tracker announce is sent (or attempted to be sent).
This alert is generated on tracker time outs, premature disconnects, invalid response or
a HTTP response other than "200 OK".
This alert is posted whenever a tracker responds with a ``trackerid``.
This alert is only for informational purpose.
This alert is triggered if the tracker reply contains a warning field.
A network address and UDP port pair for DHT and uTP protocol communication.
This alert is posted when there is an error on the UDP socket.
This alert is generated when a block is received that was not requested or
whose request timed out.
This alert is generated when a HTTP seed name lookup fails.
Utility methods for converting between Java and native C++ vector types.
Information about a web seed (HTTP/FTP server) providing torrent content.
Http seeds are different from url seeds in the
protocol they use.