Reverse order of RPL_INVITING and update readme

See https://www.rfc-editor.org/errata/eid2821 for the erratum that
caused this change.
This commit is contained in:
Les De Ridder 2017-05-18 20:26:29 +02:00
parent b8484c60d4
commit ad4b2a22ea
No known key found for this signature in database
GPG Key ID: 5EC132DFA85DB372
2 changed files with 4 additions and 4 deletions

View File

@ -6,8 +6,8 @@ salty-ircd is an [Internet Relay Chat](https://en.wikipedia.org/wiki/Internet_Re
The main goals of salty-ircd are strict RFC compliance and security.
### RFC compliance
salty-ircd aims to be fully compliant with the IRC RFCs, specifically [RFC 1459](https://tools.ietf.org/html/rfc1459), [RFC 2811](https://tools.ietf.org/html/rfc2811), [RFC 2812](https://tools.ietf.org/html/rfc2812), and [RFC 2813](https://tools.ietf.org/html/rfc2813) (planned).
Newer RFCs take precedence over older RFCs.
salty-ircd aims to be fully compliant with the IRC RFCs, specifically [RFC 1459](https://tools.ietf.org/html/rfc1459), [RFC 2811](https://tools.ietf.org/html/rfc2811), [RFC 2812](https://tools.ietf.org/html/rfc2812), and [RFC 2813](https://tools.ietf.org/html/rfc2813) (planned).
Newer RFCs take precedence over older RFCs. Errata are respected by default, with newer errata (on the same RFC) taking precedence over older errata.
Any additional features breaking RFC compliance will be made available through compile-time options.

View File

@ -1123,8 +1123,8 @@ Lforeach:
void sendRplInviting(string channelName, string name)
{
//TODO: If RFC-strictness is off, send parameters in reverse order
send(Message(_server.name, "341", [nick, channelName, name]));
//TODO: If errata are being ignored, send nick and channel name in reverse order
send(Message(_server.name, "341", [nick, name, channelName]));
}
void sendRplEndOfNames(string channelName)