> I'm also getting a very strong impression that multithreaded > listeners are best implemented in C#.
Speaking as someone who much prefers C# to VB.NET, I don't actually agree. I'm not aware of anything C# can do that makes it more able to implement a multithreaded listener than VB.NET - the same set of CLR services are available to you. I would choose C# if I were writing it simply because I know C# much better than VB.NET. If you know VB.NET better, it's probably better to go with VB.NET. > I'm particularly focused on stability, scalability and > performance (who isn't?), and suspect the rewrite should be > from the socket level rather than TcpClient. It's true that to achieve the best possible throughput you're almost certainly better of working directly with sockets, simply because you are working closer to the metal. But I've not done any performance tests to see how much difference it would make. (And this of course is a decision you can make independently of language.) -- Ian Griffiths - DevelopMentor http://www.interact-sw.co.uk/iangblog/ =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
