hi,



Apart from IIS, what other web servers can 

we use for deploying .Net Services?  



Can we use Microsoft Exchange Server 2000?



In case we use IIS web server can u please 

give me an idea of how the Scalability issues

can be governed?



Thanks.

Regards,



Uma





_____________________________________________________

Chat with your friends as soon as they come online. Get Rediff Bol at

http://bol.rediff.com

Uma,



my answers inline with ***



-----Original Message-----

From: Uma Maheswari [mailto:maheswarim@r...]

Sent: Samstag, 17. Februar 2001 10:45

To: ASP+

Subject: [aspx] What web servers does .Net services need?



hi,



Apart from IIS, what other web servers can

we use for deploying .Net Services? 



*** YOu can write your own host for most propably any other web server

you want. ASP.NET comes with a quite seimple to use API to write a host

for it - easy to use **if** you know hot wo write a web server, a

scalable one, btw.



Can we use Microsoft Exchange Server 2000?



*** Let me answer this with another question - since when does Exchange

Server 2000 be a web server? I mean, the last time I looked at Exchange

Server 2000, it was relying to IIS for handling it's web interface.



In case we use IIS web server can u please

give me an idea of how the Scalability issues

can be governed?



*** Well, now, maybe I sound utterly stupid, but what scalability

issues? I mean, in our experience, IIS has been one of the most scalable

and powerfull web servers. Most scalability issues have either been ASP

based (i.e. no support for server farms) or be caused by - sorry for the

harsh wording - utterly stupid programmers, though this was a VERY

special case.



It was actually an intranet application that was transferred to

javascript because "ASP does not scale" - now, the programmers had an

ADO connection to the database (better:ONE), which they opened in

Application.Start and then put into the application object - and then

used Application.lock in every page to actually serialize access to the

database "in order not to overload the database server". Funnily, they

were not that stupid in the JSP version, so they came to the conclusion

that ASP "does not scale".



Now, IIS in itself is one of the top performing and stable web servers

on the planet, and ASP.NET **does** handle a lot of potential problems

that ASP had - but even there, a lot is depending on the programmers

skill **not** to kill performance.



We have been able to server 1 million+ ASP pages on a dual processor

Xeon 500 system half a year ago, with the SQL Server being on the same

system, and I fully expect ASP.NET to be significant faster (you know,

benchmarking is not allowed yet). IF you have scalability problems with

this performance, and in the light of the - well - relatively low level

of knowledge your question implies, I would ***strongly*** advice that

in addition to the queries on this list, you spend the money and get

some well known professionals look on the way you want to build the

appplication. Actually its not **that** hard to make scalable

applications, but in the last years I have simply seen too many people

making errors because of **not** readin the manual that I am safe to

assume you wont make them.



*** In conclusion: yes, you can use another web server, but it wont make

any sense, no you can not use exchange - because exchange 2000 does not

come with a web server, and no, you dont have scalability problems -

besides the ones you create yourself in the applications.



*** And sorry, there are a number of articles out there on how to build

scalable applications, but you cann ot expect a deep explanation to do

this in this list :-)



*** Regards



*** Thomas Tomiczek

*** THONA Consulting