| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
style guidelines, we now have tabs
|
|
|
|
| |
for consistency.
|
| |
|
| |
|
| |
|
|
|
|
| |
underlying socket (more useful this way)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
with libevent (no packet merging)
|
| |
|
|
|
|
| |
connection of type 'ssl'
|
|
|
|
| |
message
|
| |
|
|
|
|
| |
- all connections support TLS
|
|
|
|
| |
functions - passing a sslctx now indicates you want to use SSL from the start
|
| |
|
|
|
|
| |
port multiplexing
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
setoption method (LuaSec issue I think)
|
|
|
|
| |
starttls() - fixes 5223 w/ libevent
|
|
|
|
| |
close session in response
|
| |
|
| |
|
|
|
|
| |
handler, if known
|
|
|
|
| |
negotiated - fixes offering starttls to client who are already using it (thanks darkrain and Adium)
|
|
|
|
| |
control whether keepalives are used
|
| |
|
| |
|
|
|
|
| |
server.hook_signal
|
|
|
|
| |
libevent's signal-catching interface
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|