- 08 Jun, 2014 7 commits
- 06 Jun, 2014 1 commit
-
-
louiz’ authored
-
- 05 Jun, 2014 1 commit
-
-
louiz’ authored
-
- 03 Jun, 2014 1 commit
-
-
louiz’ authored
-
- 31 May, 2014 4 commits
- 30 May, 2014 10 commits
-
-
louiz’ authored
-
louiz’ authored
fix #2452
-
louiz’ authored
-
louiz’ authored
-
louiz’ authored
-
louiz’ authored
-
louiz’ authored
-
louiz’ authored
-
louiz’ authored
-
louiz’ authored
We have two basic example commands. But it’s not entirely finished because there are some error checks that we don’t do. ref #2521
-
- 28 May, 2014 5 commits
- 27 May, 2014 5 commits
-
-
louiz’ authored
-
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
-
louiz’ authored
-
louiz’ authored
It also happens to fix #2517 because this used to create buggy channels named "auth" and stuf like that.
-
louiz’ authored
-
- 26 May, 2014 3 commits
-
-
louiz’ authored
We want to call socket() with the parameters provided by getaddrinfo, so we can’t addd the fd into the poller immediately. We need to wait the connection attempt, and then the SocketHandler can call add_socket_handler itself, if the connection succeeds, or is in progress.
-
louiz’ authored
Because the read handler may discover that the connection has been closed, and then remove the socket from the poller. It that case it is no longer valid to try to call the write handler (which may try to reconnect, but since that socket is no longer managed, this is not OK).
- 25 May, 2014 2 commits
- 14 May, 2014 1 commit
-
-
louiz’ authored
Explain that the behaviour is otherwise undefined, in the comment.
-