Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
If the client does not send a PONG message in time then they will
receive a registration timeout. The client will only receive a ping
timeout in response to a unanswered PING whilst fuilly connected to
the server.
|
|
A '.' gets added to the end of `reversedip` when creating the DNSBL
hostname for the resolver. We need to remove the trailing '.' on the
IPv6 form of `reversedip` or the resolver will fail.
|
|
|
|
Also, deprecate the old SerializeFormat/serialize/unserialise API.
|
|
Closes #1657.
|
|
|
|
Closes #1687.
|
|
Fixes #1684.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There is no reason to have these events in one big handler and it
causes unnecessary event hooks to be created by having them like
this.
The ServerEventListener class still exists for compatibility
|
|
|
|
|
|
|
|
This regression was introduced by #1659. This distinction is only
relevant on Windows so this should not affect non-Windows platforms.
|
|
There is no reason to do this.
|
|
This causes inconsistent message ids between servers.
This reverts commit 638e4bb417ebcd4f0a384ac19585620b0fde1569.
|
|
|
|
The legacy method of enabling these extensions is just a wrapper
around the capability. If the cap module is not loaded it can not
be enabled so we should not advertise it.
|
|
|
|
|
|
|
|
|
|
|
|
Also fixes accidentally copying incoming tags on TAGMSG when sending to
other users
|
|
This makes debugging issues easier.
|
|
|
|
|
|
This is essentially identical to the one for the start event.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|