TODO: Add a way to request DNS resolves from the controller

Nick Mathewson nickm at
Wed Jun 27 16:20:06 UTC 2007

On Wed, Jun 20, 2007 at 10:36:22PM +0100, Robert Hogan wrote:
> I've implemented a rudimentary version of this.
> I think I have the fundamentals right (it works) but I'm not sure about the 
> interface. The controller requests resolves with:
> 250 OK
> And tor responds with:


> Internally, performing a resolve request enables the RESOLVE event for that 
> controller. But you only get a RESOLVE event whenever you request
> one.
> I've implemented it as an event rather than a getinfo because of the
> expected latency of the response.


> This approach breaks the spec a bit, in that 650 events now occur when you 
> perform a SETEVENTS or implicity enable a RESOLVE event by performing a 
> Should I continue on the basis of this approach or is there a strong 
> preference to make the requests something like getinfo resolve/ ?

I think the approach you describe above is okay.  It shouldn't break
backward compatibility, since preexisting controllers will never issue
RESOLVE commands, and so will never get "650 RESOLVE" events.

Nick Mathewson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 652 bytes
Desc: not available
URL: <>

More information about the tor-dev mailing list