Internal processing

[Renegade334]

ref: #40

There are certain functions of a client that are essential to the client-server relationship, such as responding to server PING events.

This patch would provide a means for the client to provide such functionality as core. The method processInput() processes the parser output and performs whatever functionality is deemed fit. At the moment, two functions are performed, although more could be added:

• calling Connection::setNickname() when the server confirms that the client's nick has changed
• sending a PONG command when the client is pinged by the server

Very much up for discussion.

[coveralls]

Coverage decreased (-1.34%) to 97.48% when pulling 7b17311a4c806b4821b1bce73c1e592ac109ed85 on Renegade334:devel-internal-processing into 63d736cbfadaf0dc2948f05cc808cd12dcdbf42a on phergie:master.

[coveralls]

Coverage increased (+0.03%) to 98.86% when pulling 9271a2d9b8a17eb6092a49866fbfc05cffdf9685 on Renegade334:devel-internal-processing into 63d736cbfadaf0dc2948f05cc808cd12dcdbf42a on phergie:master.

[elazar]

@svpernova09 Note that implementing this change will effectively deprecate the Pong plugin for the bot.

Additionally, since there's no way to disable this new behavior and any existing installations that include the Pong plugin would at that point be sending two PONG events per one PING event at that point. I'm uncertain how servers will respond to that behavior; it may have no effect at all. Regardless, it's something to be aware of and something that should probably be included in release notes.

[svpernova09]

@elazar Thanks, I was going to hold off tagging this anyway. So I'll hold off until I can test if there are any ill effects of double pongs.