IIS with wshttpbinding VS windows service with netftpbinding

Which config would you recomend for a server?

I think that for a server it should be better the IIS (threads perhaps are used better than using "the iis inside framework 3.0".

What do you think?

[223 byte] By [creaturita] at [2007-12-24]

«« IE 7 RC1 SpecifyDefaultButtons
»» Assembly with Web Service is created differently b/w compile methods

# 1

What type of application are you building? Is this a service for interoperable and external consumption or internal to an application behind the firewall? Your hosting environment is a choice you make based on several things:

For WIndows 2003 server:

For interop, crossing firewalls, HTTP - use IIS/ASP.NET

For non-interop, behind firewall, intranet - use self-hosting. Either your own exe with custom code to restart and recycle service and configs, or a Windows Service if you want to have restarts handled for you. Either way, you need to write some code to handle activation, config refresh at runtime, etc. For same machine calls, named pipes, for crossing machines or creating security boundaries, TCP, for queued, reliable messaging, MSMQ.

For Longhorn: