Alexander Vieth
Alexander Vieth
I agree with @ldub and @SamProtas that > It's not necessary functionality. You could skip all tests by not running the test suite. > One solution/workaround that would satisfy my...
I personally think option 2 is the best. > I'm not too eager to do (2) at this point. Basically because once we add it, we will have to maintain...
Consider closing this since #1613 has been merged?
> In the TCP impl we will need to review carefully to make sure we can indeed guarantee the ordering of connection open/close events vs endpoint lost event. In the...
Another somewhat radical option is to give a separate egress queue. ```Haskell -- Same as is, just a renamed type. receive :: EndPoint -> IO IngressEvent -- Runs the continuation...
> Another option is to get rid of the connection bundle concept and report connections going down individually. This would need some careful thought, as I don't think the need...
https://github.com/haskell-distributed/network-transport-tests/pull/11
On second thought, this may not be a good idea. There ought to be some way to determine whether two addresses pick out the same `EndPoint` and equality strikes me...
I believe it makes sense to include `closeConnectionTo :: EndPoint -> EndPointAddress -> IO ()` in network-transport. It's not about freeing up resources, it's about controlling the event queue. Its...