Kim Alvefur <zash@zash.se> [Thu, 26 May 2022 19:24:01 +0200] rev 12528
mod_smacks: Remove debug log references to timer (not used anymore)
Cuts down on noise as well
Kim Alvefur <zash@zash.se> [Thu, 26 May 2022 17:48:59 +0200] rev 12527
Merge 0.12->trunk
Kim Alvefur <zash@zash.se> [Thu, 26 May 2022 17:38:55 +0200] rev 12526
mod_smacks: Fix to use current method of counting acked stanzas
Fixes #1757
These places seem to have been left since e62025f949f9
The logic around expected_h in should_ack() misbehaved, always comparing
with 0 + unacked instead of acked + unacked.
Kim Alvefur <zash@zash.se> [Thu, 26 May 2022 13:46:10 +0200] rev 12525
Merge 0.12->trunk
Kim Alvefur <zash@zash.se> [Thu, 26 May 2022 13:03:58 +0200] rev 12524
util.prosodyctl.check: Remove now redundant unbound config tweak
This is now done in net.unbound itself
Turning it back on in the config may still cause the problem of entries
there masking the DNS values.
Kim Alvefur <zash@zash.se> [Sat, 21 May 2022 13:11:25 +0200] rev 12523
mod_smacks: Use session logging for remaining log messages
For consistency and easier correlation of session events.
Kim Alvefur <zash@zash.se> [Fri, 11 Feb 2022 16:09:42 +0100] rev 12522
mod_smacks: Factor out some convenience functions
Those lines are long and the risk of mistakes if another one needs to be
added seems high, but lower when factored out like this.
Kim Alvefur <zash@zash.se> [Tue, 17 May 2022 17:06:36 +0200] rev 12521
util.stanza: Document top level attributes in Teal definition
Tells you if you make a typo like "gropchat" or so
Kim Alvefur <zash@zash.se> [Tue, 17 May 2022 17:05:15 +0200] rev 12520
util.stanza: Document error conditions in Teal definition
Gets you nice error messages if you make a typo in with error_reply()
Kim Alvefur <zash@zash.se> [Sun, 15 May 2022 22:41:17 +0200] rev 12519
net.server_epoll: Add option to defer accept() until data available
This is a Linux(?) socket option that delays the accept signal until
there is data available to read. E.g. with HTTP this might mean that a
whole request can be handled without going back trough another turn of
the main loop, and an initial client <stream> can be responded to.
This may have effects on latency and resource use, as the server does
not need to allocate resources until really needed.