Sure. No worms will get in the way... you'll just have to deal with denial of service attacks when receiving malformed HTML, crashed instances of the entire client when a file transfer request with parenthesis in its name is received from another user, content length memory allocation errors due to unbounded buffers, 4 isolated RTF buffer overflow issues still uncorrected, improperly formed TCP CRC headers that cause many releases of Cisco's firmware to drop the packet entirely, still improper SNAC packet handling even after they claimed it was fixed, an HTML parser who's lexer routine has a nasty memory leak that I reported to them 8 months ago and has still gone uncorrected, an infinite looping and client crash error that occurs when your system time is changed in the middle of a file transfer and the internal client timer has gone low, improper hostname resolution that results in a fatal buffer overflow, and let's not even begin to discuss the utter lack of conferencing and markup collaboration utilities for use in a real business environment.
Besides that, yeah, I'd better switch. Windows Messenger certainly isn't perfect but once again, I see your incredible line of reasoning so you've got me convinced.
This post was edited by aamendala on Sunday, March 27, 2005 at 02:56.
|