Re: [PATCH] schedule connect timeouts via eventAdd

On 25/01/2013 3:24 p.m., Rainer Weikusat wrote:
> Amos Jeffries <squid3_at_treenet.co.nz> writes:
>
> [...]
>
>> Agreed. To cut this all short. I was under the impression that we had
>> proven the usefulness of add-and-remove model.
>> Under the current code that 'remove' would be an event delete ("good
>> enough for now") with possibilities for some future improvement
>> outside the scope of this change.
> Under normal circumstance, I would have done this 'tomorrow' (whatever
> that means, considering that it is unclear for how much longer this
> nonsense will keep me awake). Considering that 'the aggressive guy'
> was finally made to deliver something (upon the immediate threat that
> someone else might do it instead), I'm going to assume that this is a
> done deal and won't bother this mailing list anymore except in case of
> 'other problems' (and even then likely not).

Please don't let this put you off. None of these problems would have
gotten halfway fixed anytime soon if it were not for your valuable time
and effort on this patch.

Alex and I have a lot of differences of opinion as to where the comm
layer scope is exactly and the whole things needs fixing/clarifying. I'm
afraid you happened to get caught in the cross-hairs of that very old
argument and I'm sorry that it has affected your experience with the
Project.

Amos
Received on Fri Jan 25 2013 - 04:45:07 MST