Add a SOURCE_ADDR field to STREAM NEW events so that controllers can match requests to applications. (Patch from Robert Hogan.)


svn:r10639

svn:r10110

 Document the nonpersistent controller-only options.


svn:r10107

 Misc cleanup and bulletproofing on r10056.


svn:r10058

so we can exit from the middle of the circuit.


svn:r10056

behavior for getinfo addr-mappings/*. this is because
the code and spec have been mismatched since at least
0.1.1.x, so i would be surprised if nobody at all is
relying on the current behavior.

backport candidate.
backbackport candidate.


svn:r9823

it a GUARD event. standardize on GUARD, but support people
asking for GUARDS too. reported by daejees.

backport candidate.


svn:r9817

svn:r9655

svn:r9650

 Make remap stream events have a souce; make them generated every time we get a successful connected or resolved cell.  Also change reported stream target address to IP consistently when we get the IP from an exit node.


svn:r9624

 twiddle signewnym rate-limiting patch so every signal gets handled eventually.  document it in control-spec. add a changelog.


svn:r9615

 Tweak stream_bw patch: Remove a couple of redundant checks, save 8 bytes per edge connection, fix spelling in the changelog; expand spec.


svn:r9586

 Apply stream_bw patch from Robert Hogan.


svn:r9585

 Mark up TODO and control-spec.txt a little.


svn:r9573

 Add a REMAP state to stream events so that controllers can learn exactly when the target address for a stream has changed.  May help Vidalia resolve confusions related to bug 375.


svn:r9484

Move specification documents into new doc/spec subdirectory.  (Proposals, drafts, and bad ideas still remain in doc.)

svn:r9411

svn:r9387

item for BW events.


svn:r9383

 Implement SOCKS_BAD_HOSTNAME status event. Defer remaining status events.  Clean up control-spec.txt a little, and fill in recommendations for events.


svn:r9374

 Patch from Mike Perry: Track reasons for OR connection failure; display them in control events. Needs review and revision.


svn:r9354

 Notes about deprecation and status events in control-spec


svn:r9320

time to put out the bugfix release.


svn:r9309

 Implement DNS-related status events.


svn:r9285

 Implement a control status event for bad libevent version/method combos.  Warn that libevent <1.1 with select() is needlessly slow.  Reply to comment.


svn:r9284

 control-spec: upcase arguments in status events; note unimplemented events individually
 r11825@Kushana:  nickm | 2007-01-03 17:41:43 -0500
 Implement EXTERNAL IP server status event.
 r11826@Kushana:  nickm | 2007-01-03 17:47:10 -0500
 Implement BAD_SERVER_DESCRIPTOR server status event.
 r11827@Kushana:  nickm | 2007-01-03 18:01:56 -0500
 Implement SOCKS_UNKNOWN_PROTOCOL and DANGEROUS_SOCKS client events.
 r11828@Kushana:  nickm | 2007-01-03 18:23:22 -0500
 Implement BUG controller events. Also, flush ERR-level status events just like ERR-level log messages.
 r11829@Kushana:  nickm | 2007-01-03 23:37:27 -0500
 Yet more status events: CLOCK_SKEW, GOOD/ACCEPTED_SERVER_DESCRIPTOR, {CHECKING_}REACHABILITY_{SUCCEEDED|FAILED}
 r11833@Kushana:  nickm | 2007-01-05 16:56:37 -0500
 Note some unimplementedness in control-spec.txt


svn:r9279

svn:r9250

what i had in mind


svn:r9241

 Implement SETEVENTS GUARD.  Needs review and testing.


svn:r9137

svn:r9109

svn:r9093

svn:r9015

yet. so be it.


svn:r8859

svn:r8855

 Fix Bug 349: Have GETINFO network-status return even old routers, and use long nicknames where appropriate.  Document this.


svn:r8834

 Add a CLEARDNSCACHE signal to clear the client-side DNS cache.


svn:r8829

 Remove reference to NS_FULL event; add two GETINFO targets.


svn:r8812

 clarify recent spec stuff


svn:r8808

some conventions.


svn:r8805

and so vidalia can start handling them if it wants.


svn:r8802

 Add an event type to tell the controller when our opinion of a router status has changed.  I might have missed some cases here.


svn:r8781