<Calimero> wrote in message news:NY********************@giganews.com...
I have to write a middleware that could be see as a very
specialized Web server (based on threads and sockets)
I hesitate between C++ (speed) and C# (more elegant)
What is the performance penalty if I use C# instead of
native (not managed) C++ ? This software could have to
manage 100's of simultanous connections. Realist in C# ?
I would say that there are many more advantages to
using C# over C++ the least of which is secure code
(no buffer overflows, etc). What little performance
difference there is can be made up for with hardware.
Hardware is cheap now. Up the processor from 2.0 to
2.5 Ghz and there you go.
The question really is, why do you feel the need
to implement some type of socket-based TCP
solution. That seems so 1990's. Web services are
the way to go. IIS is much better at handling
connections than anything you or I or most
people in this group could write, so why not
leverage what's already there and VERY well
tested?
-c