1. 22 Jun, 2014 1 commit
    • louiz’'s avatar
      Delete the timeout event using the correct socket number, instead of -1 · 7b785cf5
      louiz’ authored
      Was causing the event to not be removed in case of connection failure, which
      lead to a dangling timed event named “timeout-1”, which was called later, by
      some other SocketHandler for which even the socket creation failed (so, its
      socket is -1), with a pointer to the previous SocketHandler which has
      disappeared for a long time: segmentation fault etc.
      7b785cf5
  2. 18 Jun, 2014 1 commit
  3. 08 Jun, 2014 2 commits
  4. 28 May, 2014 1 commit
  5. 27 May, 2014 1 commit
    • louiz’'s avatar
      Only close/unmanage the socket if we are connected/connecting · 7b31bea7
      louiz’ authored
      Since the socket is now only created and managed whenever the connection is
      being established, we only close the socket and if it was created (we use -1
      to denote the fact that is not yet created, or has been closed) and we only
      unmanage the socket if it is effectively managed.
      
      fix #2529
      7b31bea7
  6. 26 May, 2014 2 commits
  7. 29 Apr, 2014 2 commits
  8. 15 Apr, 2014 2 commits
  9. 24 Mar, 2014 2 commits
  10. 09 Mar, 2014 1 commit
  11. 03 Mar, 2014 1 commit
  12. 28 Feb, 2014 1 commit
  13. 27 Feb, 2014 1 commit
  14. 22 Feb, 2014 3 commits
  15. 19 Feb, 2014 2 commits
  16. 08 Feb, 2014 3 commits
  17. 13 Jan, 2014 1 commit
  18. 04 Jan, 2014 3 commits
  19. 24 Dec, 2013 1 commit
  20. 23 Dec, 2013 1 commit
  21. 03 Dec, 2013 1 commit
  22. 10 Nov, 2013 1 commit
  23. 03 Nov, 2013 1 commit
  24. 02 Nov, 2013 3 commits