| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
| |
We need this to tell if a given consensus flavor is being downloaded
or not.
|
| |
|
|
|
|
|
|
|
|
|
| |
This requires the latest Git version of Libevent as of 24 March 2010.
In the future, we'll just say it requires Libevent 2.0.5-alpha or
later.
Since Libevent doesn't yet support hierarchical rate limit groups,
there isn't yet support for tracking relayed-bytes separately when
using the bufferevent system. If a future version does add support
for hierarchical buckets, we can add that back in.
|
| |
|
|
|
| |
Clients are now verified to work and build circuits correctly. There
are still a few warnings given here and there that I need to look into.
|
| |
|
|
|
|
| |
Also, set directory connections (linked and otherwise) to use bufferevents.
Also, stop using outbuf_flushlen anywhere except for OR connections.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
These are based strongly on connection_handle_read and
connection_handle_write, but hopefully without so much mixture of IO
logic and Tor logic.
|
| | |
|
| | |
|
| |
|