Depending on your definition of "robust server applications" .NET 2.0 is a
pretty good platform for building such applications.

If I had to build true carrier class server applications, I'm not sure if I
would choose it - but then again, I don't think there are any mainstream
platforms suitable for that level of robust.

Using 64-bit hardware and a fair bit of blood/sweat/tears we've been able to
scale our .Net server application beyond any reasonable limits that we
expect to see. You will end up learning just as much about .Net internals as
you know about Win32 internals.

The architecture you describe sounds a bit strange, to be honest. If you're
building a server application, why are you also having clients connect
directly to the database? You're mixing application architectures, and it's
likley that little good will come of it.

Some things to think about regarding the server architecture:
http://www.coversant.net/dotnetnuke/...=88&EntryID=10

.... and, of course, one of the most critical pieces: Can you debug it once
it's up and running?
http://www.coversant.net/Default.asp...=88&EntryID=28


--
Chris Mullins, MCSD.NET, MCPD:Enterprise
http://www.coversant.net/blogs/cmullins



"Cube" <SiliconJaltz05 (AT) yahoo (DOT) com> wrote