I speak about the server side. The suggested implementation is IIS. But as I am not familiar with it, I would like to know, it you have some thoughts about it, what are the upsides and downsides of each solution, IIS, service and console application.
Our application will work on an intern network, with high security. The application itself will not have security check, so maybe all the security side of IIS is not important for us. In fact, the performance and reliability will be the majors concerns.
Any thoughts?
Thanks a lot
Richard
When you think about a host, you expect certain services:
IIS/ASP.NET provide answers to all these. COM+ provides some of them, but in a different way.
A console app (or Windows Service) only provides basic process management, and relies on the stock .NET thread pool for thread management. Beyond that you have to write your own code to do the rest.
To me a Windows Service is an option of last resort. Writing, debugging and supporting all that plumbing code isn't a productive way to spend time, especially when IIS/ASP.NET already does it for you.
Thanks for the answer, Rocky. I understand it is not directly related to CSLA, so thanks to you and any other who cans help.
My knowledge about IIS is weak, so I do not see what do you mean by “thread management”. It seems to me, but maybe I am wrong, that if we have to provide some thread safe operations in the server, we have to code them thread safe, in console app or in a library on IIS. So, could you point to me the difference? Maybe, if it is too lengthy, by giving a reference to me.
In fact, probably, if someone could give a good reference (links, pdf, tutorials or books), I would be grateful. I would like to know hows IIS handles “runaway process monitoring”, “deadlock monitoring”, and “assembly shadowing”. What is that, by the way :) ?
Thanks again to all
Richard
Copyright (c) Marimer LLC