| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\| |
|
| | |
|
| |
| |
| |
| | |
actually detected
|
|/ |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| | |
select loop (which makes util.timer the only timer using server_select._addtimer).
|
|/ |
|
| |
|
|
|
|
| |
like server_event
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
handler:close() or handler:force_close() - fixes cases where ondisconnect() could be called multiple times for the same connection, leading to issues with s2sout retry logic.
|
|
|
|
| |
always call ondisconnect (with err == nil), and never close with data in send buffer (i.e. 'now' parameter removed)
|
|
|
|
| |
wasn't working anyway)
|
|
|
|
| |
ourselves (fixes HTTP session hoarding, thanks Maranda)
|
|
|
|
| |
Zash)
|
|
|
|
| |
these three modules. server.addtimer() is no longer a public function (renamed to _addtimer) and is not available at all from server_event (compat code removed to prevent traceback) (thanks Nulani)
|
| |
|
|
|
|
| |
setup to avoid a traceback (#262) (thanks Maranda)
|
| |
|
| |
|
|
|
|
| |
doesn't have an onconnect handler
|
|
|
|
| |
callbacks (thanks darkrain)
|
|
|
|
| |
onconnect being called before handshake completion for straight-SSL
|
|
|
|
| |
shows correctly when a handshake exceeded max. allowed iterations)
|
|
|
|
| |
checked despite it not being possible for them to be other than nil
|
|
|
|
| |
a handler, it doesn't mean anything
|
|
|
|
| |
addresses
|
| |
|
|
|
|
| |
for wantread and wantwrite
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
handler, in case onconnect sends data and the socket is still writeable (causing stack overflow into sendbuffer()/onconnect())
|