A note on scanning for eol tokens, whatever they may be, come on, it doesn't
take any cpu...incoming data is rather small, even on a big hub, dch++ for
instance doesn't take more than 4-5% cpu overall on a 1500 user hub (1ghz
cpu...), and I can assure you that less than 0.01% of that goes to scanning
for the end of line...therefore, imho, no command lengths in
binary...although I dislike the fact that \r\n are two characters, I tend to
agree that it's good following standards, and since millions of web servers
etc can handle millions of connections, I don't really see the problem...I
mean, wake up, turn on your profiler and have a look at where the cpu usage
goes, I can promise you it isn't strcmp in onincomingdata...

/J