File

README @ 10486:479e96e554c8

net.server_epoll: Add debug logging for delayed reading In :onreadable, if there is still buffered incoming data after reading from the socket (as indicated by the :dirty method, usually because LuaSocket has an 8k buffer that's full but it read a smaller amount), another attempt to read is scheduled via this :pausefor method. This is also called from some other places where it would be pointless to read because there shouldn't be any data. In the delayed read case, this should report that the socket is "dirty". If it reports that the socket is "clean" then the question is where the buffer contents went? If this doesn't get logged after the scheduled time (0.000001s by default) then this would suggests a problem with timer or scheduling.
author Kim Alvefur <zash@zash.se>
date Sat, 07 Dec 2019 19:05:10 +0100
parent 9945:606b2567ff18
child 10692:a0480ee2233a
line wrap: on
line source

# Prosody IM Server

## Description

Prosody is a server for Jabber/XMPP written in Lua. It aims to be easy 
to use and light on resources. For developers, it aims to give a 
flexible system on which to rapidly develop added functionality or 
rapidly prototype new protocols.

## Useful links

Homepage:        https://prosody.im/
Download:        https://prosody.im/download
Documentation:   https://prosody.im/doc/
Issue tracker:   https://issues.prosody.im/

Jabber/XMPP Chat:
               Address:
                 prosody@conference.prosody.im
               Web interface:
                 https://prosody.im/webchat
               
Mailing lists:
               User support and discussion:
                 https://groups.google.com/group/prosody-users
               
               Development discussion:
                 https://groups.google.com/group/prosody-dev
               
## Installation

See the accompanying INSTALL file for help on building Prosody from source. Alternatively 
see our guide at https://prosody.im/doc/install