Managed Projects

aria2

  Analyzed about 1 month ago

aria2 is a utility for downloading files. The supported protocols are HTTP(S), FTP, BitTorrent (DHT, PEX, MSE/PE), and Metalink. It can download one or more files individually or from multiple sources/protocols at the same time and tries to utilize your maximum download bandwidth (by using ... [More] multiple threads and downloading data from HTTP(S)/FTP, while also uploading to the BitTorrent swarm). Using Metalink's chunk checksums, aria2 automatically validates chunks of data while downloading a file like BitTorrent. The physical memory usage is typically 3MB(normal HTTP/FTP downloads) to 6MB(BitTorrent downloads). CPU usage in BitTorrent with download speed of 1500KB/sec is around 6%. [Less]

129K lines of code

4 current contributors

10 months since last commit

146 users on Open Hub

Activity Not Available
4.65
   
I Use This

apt-metalink

  Analyzed about 1 month ago

apt-metalink allows you to download Debian/Ubuntu packages from several sources concurrently and makes upgrade process faster. apt-metalink uses python-apt to interface apt infrastructure and aria2 as download back-end. Metalink is used to feed package list to aria2.

230 lines of code

0 current contributors

about 2 years since last commit

2 users on Open Hub

Activity Not Available
0.0
 
I Use This

argparse4j

  Analyzed about 1 month ago

Java port of Python's famous argparse command-line argument parser.

9.78K lines of code

2 current contributors

about 4 years since last commit

1 users on Open Hub

Activity Not Available
0.0
 
I Use This

Spdylay

  Analyzed about 1 month ago

This is an experimental implementation of Google's SPDY protocol version 2 and 3 in C.

32.6K lines of code

0 current contributors

over 8 years since last commit

1 users on Open Hub

Activity Not Available
0.0
 
I Use This
Tags spdy

wslay

  Analyzed about 1 month ago

Wslay is a WebSocket library written in C. It implements the protocol version 13 described in RFC 6455. This library offers 2 levels of API: event-based API and frame-based low-level API. For event-based API, it is suitable for non-blocking reactor pattern style. You can set callbacks in various ... [More] events. For frame-based API, you can send WebSocket frame directly. Wslay only supports data transfer part of WebSocket protocol and does not perform opening handshake in HTTP. Wslay does not perform any I/O operations for its own. Instead, it offers callbacks for them. This makes Wslay independent on any I/O frameworks, SSL, sockets, etc. This makes Wslay protable across various platforms and the application authors can choose freely IO frameworks. [Less]

5.43K lines of code

0 current contributors

over 2 years since last commit

0 users on Open Hub

Activity Not Available
0.0
 
I Use This