-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing JOIN parse #1049
Fixing JOIN parse #1049
Conversation
Ah, right, the old code was something like:
But the new code messed it when was converted to binary:
However, your solution isn't yet fully equivalent:
This would be better, right? Can you confirm this third solution is better?
|
I am so sorry but I'm not good with erlang and I don't understand the difference with 2 and 3 in your examples. Now the code i submitted is:
What would you change here? Thanks. |
The difference between 2 and 3 is the character between _ and Chan: you put | and I put , because that way the result is more correct, apparently. |
You're right, what you say fixes JOIN and NICK messages. |
Hi, why did you close it ? |
Because I noticed it is failing and I want to submit it with more patches. In general I see that a lot of things have to be improved more closed to the IRC protocol. For example, KICK messages are not sending the information in a proper way for a web client. |
ok, fine then. Please, keep us posted :) |
Maybe you can help me with some doubts. Why it is sending two stanza for some single IRC line? It could be done with only one. This happens in multiple places, for example process_kick(). |
@badlop any idea about this question ? |
For now, I'm fixing some messages and adding some parameters to isolate parts of the IRC protocol messages. For example, in KICK, I've added the param moderator to be able to get it in the client as the one who kicks the user and message to get the kick message. What was happening also is that if kick message had :, this was truncated to the string since the last :. I've also added message parameter to isolate the part and quit messages. For now I'm planning to send the 366 numeric message (end of /names) to be able to, when client receives it, render all previous users & channel user count all at once in the web client jQuery app I'm coding to improve performance. When I finish, I will post it here with all modifications and the reasons why I did it. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The parse of JOIN was wrong. Channel name its after :#, not before.