#!/usr/bin/env python

"""

The BitTorrentClient sets up necessary objects before creating a Reactor and

calling run on it to start the event loop. From there all other functions of

the BitTorrent client are event driven and flow from calls from the Reactor.

Initially, the client chooses a peer_id and creates an Acceptor for incoming

connections. Before starting the reactor, it schedules a call to

start_download which eventually creates a TorrentMgr for each torrent specified

on the command line.

Since uploading is not yet fully supported, the place of the Acceptor in the

system hasn't fully been thought out. When the Acceptor presents an incoming

connection, a PeerProxy must be created with the connection and it should

handshake with the peer. After the handshake, it can be determined which

torrent the peer wishes to upload and the PeerProxy can be added to the

appropriate torrent. It's not clear whether this functionality belongs in the

BitTorrentClient or perhaps in an incoming connection manager.

Right now, nothing handles cleanup on program exit. Files should be flushed

and closed and sockets should be closed ideally.

"""

import logging

import logging.config

import sys

import time

from acceptor import Acceptor

from reactor import Reactor

from torrentmgr import TorrentMgr

from torrentmgr import TorrentMgrError

_PORT_FIRST = 6881

_PORT_LAST = 6889

logging.config.fileConfig('logging.conf')

logger = logging.getLogger('bt')

class BitTorrentClient(object):

pass

if __name__ == '__main__':

if len(sys.argv) == 1:

print("usage: {0} file1 [file2 ...]".format(sys.argv[0]))

print(" file1, file2, etc.: torrent files")

sys.exit(1)

logger.info("Starting BitTorrent Client")

BitTorrentClient()