[jdev] All together now...

[Chris Mullins]

[Server Error Checking]
 
Norman Rasmussen Wrote:
> I would be doing exactly the same as the google croud are.  
> If the connection breaks the spec - drop it fast.  
 
hah. That might work for Google, but not for anyone else. 
 
The support email goes something like:
Them: "i installed ur server. i trid to konnekt butt ghott errr. mi klient wrks gr8 with jabber 6.02E23, so ur server sux.".
 
Us: "Thanks for installing our server. Unfortunatly you're using a non-complient client that hasn't been updated by the author in 3.5 years and is based on a language that predates Latin. Please upgrade to any of the modern clients, here's a list of ones we've tested with."
 
Them: "u suk. we rolld out 6000 copies of our kik azz client, and r not going to change 4 u. m8ke it work!!!!!!!!"
 
Us: "Sigh. Ok. We give in. Throw this switch in the config file and it will work."
 
Unfortunatly this scenario seems to be very common with the smaller deployments, and a surprising number of the big ones.
 
-- 
Chris Mullins
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 4359 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20060117/2dded186/attachment-0002.bin>