Closed peol closed 12 years ago
Some servers are completely silent until the client sends some message. See https://github.com/gf3/IRC-js/commit/bfa34db
So this issue is completely fixed by that commit?
God damn GH, don't have "Comment & close" closest to the textbox :P
Oops, no. That commit is about different level of connecting. But I think that Jerk should listen for 'connected' event at that point instead of waiting to receive some irc message.
Indeed, the problem is that the connected
stuff isn't available everywhere. Most servers accepts the client spamming JOIN etc. before actually being fully connected, but the fallback being PING/PONG, this is a better alternative (just look up a RAW IRC code that specific server is spitting out).
Hmm, connected event is issued by irc-js when it has sent ( asynchronously ) the login commands to the server. Maybe it should issue the event after the server has accepted the login. Note that connected event is distinct from the connect even emitted by the networking lib.
Yeah, you're right. I think it should fire after the login stuff has been sent, that's what connected
means in my world when it comes to IRC :)
Added an additional 'trigger on-connect' override called
joinOn
, which accepts a raw IRC protocol code