Matthew Wild <mwild1@gmail.com> [Fri, 23 Feb 2018 16:23:03 +0000] rev 8539
net.connect: Default to *a pattern if none provided
Matthew Wild <mwild1@gmail.com> [Fri, 23 Feb 2018 16:21:40 +0000] rev 8538
net.http: Rename handler to conn, for consistency with all our other code
Matthew Wild <mwild1@gmail.com> [Fri, 23 Feb 2018 16:20:45 +0000] rev 8537
net.http: Remove use of 'conn' (raw socket object returned by addclient)
Kim Alvefur <zash@zash.se> [Fri, 23 Feb 2018 17:11:59 +0100] rev 8536
moduleapi: Remove unused and undocumented :has_feature and :has_identity
Kim Alvefur <zash@zash.se> [Fri, 23 Feb 2018 17:10:21 +0100] rev 8535
doc: Add template / API specification for net.server (thanks Daurnimator)
Matthew Wild <mwild1@gmail.com> [Fri, 23 Feb 2018 15:53:45 +0000] rev 8534
net.connect: New API for outgoing connections, based on 'service resolvers'
Matthew Wild <mwild1@gmail.com> [Fri, 23 Feb 2018 15:41:12 +0000] rev 8533
net.server_event: Not every instantly-readable connection is an error, continue if possible
Matthew Wild <mwild1@gmail.com> [Fri, 23 Feb 2018 15:33:02 +0000] rev 8532
net.server_event: Better outgoing connection error handling
Same as 67311cda0625. Check for readability. If a socket is readable
after initial connection, it likely means an error, so we call the
readcallback for that connection to handle it (and ultimately close).
Matthew Wild <mwild1@gmail.com> [Fri, 23 Feb 2018 15:30:00 +0000] rev 8531
net.server_select: Better detection of errors for outgoing connections
On connection failure, a socket is marked readable and writable. So
to detect initial connection failures (connection refused, etc.) we
now watch for sockets becoming readable during initial connection,
and also read from readable sockets before writing to writable
sockets.
This should fix 'onconnect' being called for outgoing connections
that actually failed.
Jonas Wielicki <jonas@wielicki.name> [Fri, 23 Feb 2018 14:07:16 +0100] rev 8530
MUC: Emit 333 status code on presence as per XEP-0045 1.30 (fixes #1087)