{"push_id":947458208,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"523c6e5ca1d16eab6988aa8fcc138dfbfff5edb4","before":"3336f19fa9a0ecc0e14afe55f38c7cd1a6cdbb50","commits":[{"sha":"523c6e5ca1d16eab6988aa8fcc138dfbfff5edb4","author":{"email":"35a2c6fae61f8077aab61faa4019722abf05093c@jonasborjesson.com","name":"Jonas Borjesson"},"message":"Allowing to lookup flows based on endpoint id.\n\nUsually, if you just ask to connect to a remote ip:port over a certain transport, such as TCP, you don't\ncare which existing flow to use as long it is indeed connected to that remote host. So, you may have\nmultiple TCP connection connected to that remote host and therefore we should allow to use\nany of those, which we now do.\n\nPreviously, an issue was that we created a new ConnectionId based on the local listening address\nfor a particular network interface but if it was TCP, then of course, there will never ever\nbe an outgoing connection from that listening port which meant we created a new flow\nevery time! That has been fixed.\n\nHaven't fixed all unit tests yet but wanted to check it in so I don't loose it...","distinct":true,"url":"https://api.github.com/repos/jonbo372/sipstack/commits/523c6e5ca1d16eab6988aa8fcc138dfbfff5edb4"}]}