Mathieu Boespflug
Mathieu Boespflug
> We'll leave this issue open a week for potential objections. A bit more than a week later... did anything become of this function? Is it now documented and official?
So how do we reconcile this: @maoe writes > I agree that it would be great if we could just use the upstream version. It was a bit painful to...
@maoe yup, sounds good to me.
Does anyone even need the write-back-to-disk functionality? It seems like an odd feature to me to be able to write our own event logs when we're not the compiler. If...
Note that the loopback interface does not always have address 127.0.0.1 on all systems.
_From @edsko on November 6, 2012 14:42_ We started to do this for Network.Transport.TCP, and it's quite aways there, but not quite done yet.
Notice that this feature request amounts to adding the same function as what d-p-tests expect in order to break connections between two endpoints for testing purposes. I guess this issue...
For the C.D.P.Node specific use case, a failed connection, as opposed to a closed connection, is the only reasonable semantics, from the moment that we want to consider that the...
This ticket is about tearing down an entire heavyweight connection (i.e. many lightweight connections in one go) when a problem was encountered. And tearing it down without the cooperation of...
_From @robstewart57 on December 18, 2012 14:31_ I'm not sure if this sits in this issue... I'd like to further this by suggesting that some autonomous management should be done...