On Sun, Jun 19, 2011 at 11:18 AM, Damian Johnson wrote:
>> you and atagar...
>
> I am atagar.
LOL! It's a small world, eh?
> All the concurrency issues for shutting down should have been
> addressed. What sort of problems are you encountering? Do you have a
> use case for reproducing the issue?
> you and atagar...
I am atagar.
> atagar's timeout was way too short in my testing.
I picked 20 ms because that's the runtime for fast queries, like
'GETINFO version'. There was a tradeoff in picking the timeout
duration, but since it was within a loop it didn't impact correctness.
Lowering mea
On Sun, Jun 19, 2011 at 9:55 AM, Damian Johnson wrote:
>> Is there a defined timeout for the TOR control protocol? How long
>> should a control port client wait around for socket data when reading?
>> Or writing? The only references to timeouts that I find in
>> control-spec.txt are about circ
> Is there a defined timeout for the TOR control protocol? How long
> should a control port client wait around for socket data when reading?
> Or writing? The only references to timeouts that I find in
> control-spec.txt are about circuit and stream timeouts reported back
> through the control
Is there a defined timeout for the TOR control protocol? How long
should a control port client wait around for socket data when reading?
Or writing? The only references to timeouts that I find in
control-spec.txt are about circuit and stream timeouts reported back
through the control port.
--
