The CHAT command was implemented during a time when we didn't use worker
threads;
every session was bound to one socket and one thread, and that was it.
Yes, we'll get past that, but NOT RIGHT NOW!!
Also keep in mind that START_CHAT_MODE is also used in some other places,
for example,
but the client is intended to send the message then and terminate, right?
so its one command which may consist of two back and forth iterations?
I don't see much sense debugging it in the state its currently in.
So let me get this straight ... the chat code that has been working fine
for 12 years, needs to be rewritten because it doesn't work nicely anymore
after you changed the transport underneath it?
This is my problem why?
Sa Mär 27 2010 13:45:43 EDT von IGnatius T Foobar @ Uncensored Betreff: Re: cmd_chat
I don't see much sense debugging it in the state its currently in.
So let me get this straight ... the chat code that has been working fine for 12 years, needs to be rewritten because it doesn't work
Ok, well I do agree that the chat protocol is suboptimal and needs to be
rewritten
.. just not during a feature freeze. In the future we should make the chat
protocol look more like the instant message protocol.
If we need to stop the bleeding, right now we could just disable the server
