#974 mod_smacks causes two TCP segments to be sent
Whenever mod_smacks issues an <r/> over a session, it will do session.send right after the stanza that caused the transmission (every stanza by default) has been sent.
That means, the transmission goes like that:
--> <r/> (Nagle's algorithm makes the TCP stack wait for the ack until sending out the next incomplete segment)
It would be great if prosody could piggy-back the <r/> on the stanza(s) segment, to reduce the number of round trips and the battery drain on mobile clients. Thanks.
Tagging issue as affecting a community module, not officially supported by the Prosody team.