Paolo Bonzini writes:
> Il 17/10/2012 16:43, Markus Armbruster ha scritto:
>>> > Error propagation is already there for socket backends, even though
>>> > it is (and remains) incomplete because no Error is passed to the
>>> > NonBlockingConnectHandler.
>> Why is that a problem?
>
> It means that
Il 17/10/2012 16:43, Markus Armbruster ha scritto:
>> > Error propagation is already there for socket backends, even though
>> > it is (and remains) incomplete because no Error is passed to the
>> > NonBlockingConnectHandler.
> Why is that a problem?
It means that the exact error message still can
Paolo Bonzini writes:
> Error propagation is already there for socket backends, even though
> it is (and remains) incomplete because no Error is passed to the
> NonBlockingConnectHandler.
Why is that a problem?
> Add it to other protocols, simplifying
> code that tes
Error propagation is already there for socket backends, even though
it is (and remains) incomplete because no Error is passed to the
NonBlockingConnectHandler. Add it to other protocols, simplifying
code that tests for errors that will never happen.
With all protocols understanding Error, the cod
