Thank you for your reply.
Fiendish said:
What would you say if you sent a command and you saw the output immediately but someone else in the room did not see it for 30 seconds? You would say the other person is lagging or something, right? Or it could be a bug in the server or some other problem entirely. That is why I don't think you can automatically say that there is no network or server problem just because someone else saw your commands.
The two char is in my two world of the same mushclient process. So I guest that it's not caused by the network delay.
What I happened is that one char send command, but can't see the echo. Another char in the same room can see the echo. The two char are in the same muchclient process.
Fiendish said:
Now you say that mcclient does not do anything, just acts as passthrough, for this data. If it doesn't do anything, how can it make the problem go away?
Sorry, I mean that mcclient does not compress or decompress in my case. Mcclient may collect the data from server and send to mushclient line by line. and it means mushclient may has bug when recieve parts of lines, right?
It block the msg for a few munites, which is obviously out of the network delay time.
I hope that mushclient will be better and better. And it's a good chance to catch the bug. |