jiigen666/libtorrent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

*** empty log message ***

Browse Source
This commit is contained in:
Arvid Norberg
2004-01-19 19:36:55 +00:00
parent eda50ceeb5
commit b9c3db8a07
14 changed files with 231 additions and 101 deletions
Download Patch File Download Diff File Expand all files Collapse all files

52
docs/manual.rst
View File

@@ -38,7 +38,8 @@ The current state includes the following features:
of a resumed torrent. Saves the storage state, piece_picker state as well as all local
peers in a separate fast-resume file.
* Supports the extension protocol `described by Nolar`__. See extensions_.
* Supports files > 2 gigabytes (currently only on windows)
* Supports files > 2 gigabytes (currently only on windows).
* Supports the ``no_peer_id=1`` extension that will ease the load off trackers.
__ http://home.elp.rr.com/tur/multitracker-spec.txt
.. _Azureus: http://azureus.sourceforge.net
@@ -1127,7 +1128,8 @@ as severity level ``debug``.
invalid_request_alert
---------------------
Thie is a debug alert that is generated by an incoming invalid piece request.
This is a debug alert that is generated by an incoming invalid piece request. It is
generated as severity level ``debug``.
::
@@ -1147,32 +1149,52 @@ Thie is a debug alert that is generated by an incoming invalid piece request.
};
torrent_finished_alert
----------------------
chat_message_alert
------------------
This alert is generated when you receive a chat message from another peer. Chat messages
are supported as an extension ("chat"). It is generated as severity level ``critical``,
even though it doesn't necessarily require any user intervention, it's high priority
since you would almost never want to ignore such a message. The alert class contain
a torrent_handle_ to the torrent in which the sender-peer is a member and the peer_id
of the sending peer.
This alert is generated when a torrent switches from being a downloader to a seed.
It will only be generated once per torrent. It contains a torrent_handle to the
torrent in question. This alert is generated as severity level ``info``.
::
struct chat_message_alert: alert
struct torrent_finished_alert: alert
{
chat_message_alert(const torrent_handle& h
, const peer_id& sender
torrent_finished_alert(
const torrent_handle& h
, const std::string& msg);
virtual std::auto_ptr<alert> clone() const;
torrent_handle handle;
peer_id sender;
};
.. chat_message_alert
------------------
This alert is generated when you receive a chat message from another peer. Chat messages
are supported as an extension ("chat"). It is generated as severity level ``critical``,
even though it doesn't necessarily require any user intervention, it's high priority
since you would almost never want to ignore such a message. The alert class contain
a torrent_handle_ to the torrent in which the sender-peer is a member and the peer_id
of the sending peer.
::
struct chat_message_alert: alert
{
chat_message_alert(const torrent_handle& h
, const peer_id& sender
, const std::string& msg);
virtual std::auto_ptr<alert> clone() const;
torrent_handle handle;
peer_id sender;
};
dispatcher
----------