L

libertasretis

Settings | Report Duplicate

0

I Use This!

Inactive

Commits : Listings

Analyzed about 1 hour ago. based on code collected about 4 hours ago.

Commit Message	Contributor	Files Modified	Lines Added	Lines Removed	Code Location	Date
Apr 24, 2023 — Apr 24, 2024 Showing page 1 of 3 Search / Filter on:
implemented connection_in updated some in-file documentation	machitu	More...				almost 7 years ago
corrected spelling mistakes	machitu	More...				almost 7 years ago
work-in-progress 1. started modularization of connection management for peerwire protocol; each connection should be managed in its own thread 2. incoming connections and outgoing connections have separate implementations, but both converge once handshake is realized 3. Bit Torrent protocol implementation has been given its own module 4. incoming connection is not yet implemented	machitu	More...				almost 7 years ago
cleanup	machitu	More...				almost 8 years ago
updated documentation	machitu	More...				almost 8 years ago
updated docs for new release	machitu	More...				almost 8 years ago
tracker protocol is now a multiprocessing.Processs instance in order to be terminated when user gives command; otherwise a Thread waits until HTTP connection timeouts added another option for development; if fifth option is set to 'development', waiting period for peerwire protocol is set to 10 seconds in order to not clutter logs	machitu	More...				almost 8 years ago
bugfix: syntax error	machitu	More...				almost 8 years ago
marked as DEPRECATED some variables; cleanup; brought function and class docs up to date	machitu	More...				almost 8 years ago
removed last references to to_connect and to_disconnect lists	machitu	More...				almost 8 years ago
updated ChangeLog	machitu	More...				almost 8 years ago
lrnet: eliminated the thread for running peerwire connections peerwire protocol: build Asynchat subclass only when connecting to remote peer all: use dictionary ("swarm") for peers; server and peerwire protocol add to this dictionary	machitu	More...				almost 8 years ago
mark working time for disconnected, connected and handhaked peers: disconnected when trying to connect, connected and handshaked always	machitu	More...				almost 8 years ago
moved peer processing in specific functions, for each state (disconnected, connected, handshaked)	machitu	More...				almost 8 years ago
removed logging from TODO	machitu	More...				over 9 years ago
Added logging. See ChangeLog for Details.	machitu	More...				over 9 years ago
Workaround for nondeterministic DNS resolving for UDP trackers. Added UDP error message parsing.	machitu	More...				over 9 years ago
Updated documentation. See NEWS, README and ChangeLog for details.	machitu	More...				over 10 years ago
Removed command line options. Use positional arguments.	machitu	More...				over 10 years ago
finished implementing UDP tracker protocol	machitu	More...				over 10 years ago
* fixed typos * fixed syntax errors	machitu	More...				over 10 years ago
don't save empty peers list	machitu	More...				over 10 years ago
implemented encoding and decoding of messages belonging to UDP tracker protocol	machitu	More...				over 10 years ago
implemented cycle of udp tracker protocol (no encoding or decoding of udp tracker protocol messages)	machitu	More...				over 10 years ago
Foundation for multiple types of tracker URLs. See ChangeLog for details.	machitu	More...				over 10 years ago
updated source code documentation	machitu	More...				over 10 years ago
Bugfix: after implementing correctly multitracker protocol, tracker thread was not responding to user commands (revealed bug). Solved it (now tracker thread exits immediately after finishing the attempt to connect to tracker, if command is 'stop' or 'quit').	machitu	More...				over 10 years ago
Updated changelog.	machitu	More...				over 10 years ago
Bugfix: wasn't passing over all URL in one pass, but only one URL was used, so implemented proper processing of multitracker case as follows: all URLs in each tier are checked before going to next tier. URLs within each tier are processed in a randomly chosen order, i.e. the tracker list is shuffled at initialization of trackerprotocol module and then parsed in order; if a connection with a tracker succeeds, the tracker URL is moved to the front of the tier.	machitu	More...				over 10 years ago
updated documentation	machitu	More...				almost 11 years ago

←
1
2
3
→