[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: getinfo circuit-status

To: or-talk@xxxxxxxxxxxxx
Subject: Re: getinfo circuit-status
From: Nick Mathewson <nickm@xxxxxxxxxxxxx>
Date: Mon, 15 Feb 2010 14:19:24 -0500
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Mon, 15 Feb 2010 14:19:32 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=4cdYBmczgq4PHcfr9bPCxqXIr9697AIL7xyOlKjt2WM=; b=HcL0MTnW7KmOfSCotSvapCx+BpyxW+hPzgL7tgSFlKjn6YvU0EUb5GRi1AWSuTpiUY LSRfKzAmu0LtE6JkUTxioDGhnzgQZAk0jjOkvpItVk+0zUWigNANI0xU9Nx0N+KgZA/B Fsd3x0hvzdi0l1cYyTlE2YPo4gtLov8sqmCA0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=cvxuQNIRA/GVnDZDnnMODakNtsQLspgznNdZLsZPcF3ymqY+qLFko3Z96SGT9BDhDx vGOywbHtLcPqrkxUirQ0Z7SQn57hbxxqLV3MeXrdcerEfUAO1rnmi/DzDwrzEpzxTwEW OhceB+8JyfH+SZPnpzYLC0nsx8RW/lRYVCfb0=
In-reply-to: <4B799DCC.2000108@xxxxxxxxxxxx>
References: <20100211090316.12681e83ehzzkiis@xxxxxxxxxxxxxxxxx> <CBA06EB04B504BD0BABE5A3B11769C70@Heron> <4B7709DF.7050904@xxxxxxxxxxxx> <e8ac78311002150952r616bbdeo4ca3452752b1b4b8@xxxxxxxxxxxxxx> <4B799DCC.2000108@xxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx

On Mon, Feb 15, 2010 at 2:17 PM, Nico Weinreich <info@xxxxxxxxxxxx> wrote:
 [...]
> OK, thanks for this very detailed explaination. But is there a way to get
> (before or after a HTTP request) the circuit which will be (or was) used?

If you watch for STREAM events, you'll learn which streams get
attached to which circuits.

-- 
Nick
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/

References:
- ressource problem on linux?
  - From: info
- Re: ressource problem on linux?
  - From: Nico Weinreich
- getinfo circuit-status
  - From: Nico Weinreich
- Re: getinfo circuit-status
  - From: Nick Mathewson
- Re: getinfo circuit-status
  - From: Nico Weinreich

Prev by Author: Re: getinfo circuit-status
Next by Author: Re: ressource problem on linux?
Previous by thread: Re: getinfo circuit-status
Next by thread: Re: getinfo circuit-status
Index(es):
- Author
- Thread