IRC Server constraint message's length, but mIRC.. - 29/09/10 04:53 AM
Using mIRC 7.1.
IRC Server may constraint message's length, but mIRC client doesn't seems aware of it.
This is maybe not a mIRC bug, but maybe a server specific behavior. I was testing some text catching script and while testing, I found out my text was either spread on multiple line or that it was truncated.
This was done on EFNet, #test100
First case:
If I send a text message to the channel:
This is a test#1. This is a test#2. This is a test#3. This is a test#4. This is a test#5. This is a test#6. This is a test#7. This is a test#8. This is a test#9. This is a test#10. This is a test#11. This is a test#12. This is a test#13. This is a test#14. This is a test#15. This is a test#16. This is a test#17. This is a test#18. This is a test#19. This is a test#20. This is a test#21. This is a test#22. This is a test#23. This is a test#24. This is a test#25.
On the other side I see this:
[09:11] <ZokciM> This is a test#1. This is a test#2. This is a test#3. This is a test#4. This is a test#5. This is a test#6. This is a test#7. This is a test#8. This is a test#9. This is a test#10. This is a test#11. This is a test#12. This is a test#13. This is a test#14. This is a test#15. This is a test#16. This is a test#17. This is a test#18. This is a test#19. This is a test#20. This is a test#21. This
[09:11] <ZokciM> is a test#22. This is a test#23. This is a test#24. This is a test#25.
We can see that the message was spread in two message. Me the sender, I don't know that this happened. Might be nice to see it exactly the same as the other side see... but chance are it is a server behavior and there is no way to tell?
I tried the exact same test with a channel notice:
/notice #test100 This is a test#1. This is a test#2. This is a test#3. This is a test#4. This is a test#5. This is a test#6. This is a test#7. This is a test#8. This is a test#9. This is a test#10. This is a test#11. This is a test#12. This is a test#13. This is a test#14. This is a test#15. This is a test#16. This is a test#17. This is a test#18. This is a test#19. This is a test#20. This is a test#21. This is a test#22. This is a test#23. This is a test#24. This is a test#25.
On the other side I see this:
[09:13] -ZokciM:#test100- This is a test#1. This is a test#2. This is a test#3. This is a test#4. This is a test#5. This is a test#6. This is a test#7. This is a test#8. This is a test#9. This is a test#10. This is a test#11. This is a test#12. This is a test#13. This is a test#14. This is a test#15. This is a test#16. This is a test#17. This is a test#18. This is a test#19. This is a test#20. This is a test#21. This is a test#22. This is a test#23. This is a test#24
You can notice that the message was truncated at "[...] This is a test#24" and therefore is missing the ". This is a test#25." part. This is more problematic than the first case as the other side miss some part of the message.
If it is server specific behavior, then is there a way for mIRC to find out max message length, max notice length, etc.
Well that's.
IRC Server may constraint message's length, but mIRC client doesn't seems aware of it.
This is maybe not a mIRC bug, but maybe a server specific behavior. I was testing some text catching script and while testing, I found out my text was either spread on multiple line or that it was truncated.
This was done on EFNet, #test100
First case:
If I send a text message to the channel:
This is a test#1. This is a test#2. This is a test#3. This is a test#4. This is a test#5. This is a test#6. This is a test#7. This is a test#8. This is a test#9. This is a test#10. This is a test#11. This is a test#12. This is a test#13. This is a test#14. This is a test#15. This is a test#16. This is a test#17. This is a test#18. This is a test#19. This is a test#20. This is a test#21. This is a test#22. This is a test#23. This is a test#24. This is a test#25.
On the other side I see this:
[09:11] <ZokciM> This is a test#1. This is a test#2. This is a test#3. This is a test#4. This is a test#5. This is a test#6. This is a test#7. This is a test#8. This is a test#9. This is a test#10. This is a test#11. This is a test#12. This is a test#13. This is a test#14. This is a test#15. This is a test#16. This is a test#17. This is a test#18. This is a test#19. This is a test#20. This is a test#21. This
[09:11] <ZokciM> is a test#22. This is a test#23. This is a test#24. This is a test#25.
We can see that the message was spread in two message. Me the sender, I don't know that this happened. Might be nice to see it exactly the same as the other side see... but chance are it is a server behavior and there is no way to tell?
I tried the exact same test with a channel notice:
/notice #test100 This is a test#1. This is a test#2. This is a test#3. This is a test#4. This is a test#5. This is a test#6. This is a test#7. This is a test#8. This is a test#9. This is a test#10. This is a test#11. This is a test#12. This is a test#13. This is a test#14. This is a test#15. This is a test#16. This is a test#17. This is a test#18. This is a test#19. This is a test#20. This is a test#21. This is a test#22. This is a test#23. This is a test#24. This is a test#25.
On the other side I see this:
[09:13] -ZokciM:#test100- This is a test#1. This is a test#2. This is a test#3. This is a test#4. This is a test#5. This is a test#6. This is a test#7. This is a test#8. This is a test#9. This is a test#10. This is a test#11. This is a test#12. This is a test#13. This is a test#14. This is a test#15. This is a test#16. This is a test#17. This is a test#18. This is a test#19. This is a test#20. This is a test#21. This is a test#22. This is a test#23. This is a test#24
You can notice that the message was truncated at "[...] This is a test#24" and therefore is missing the ". This is a test#25." part. This is more problematic than the first case as the other side miss some part of the message.
If it is server specific behavior, then is there a way for mIRC to find out max message length, max notice length, etc.
Well that's.