Question:
1. Can we say .NET 2.0 framework is an application server layer?
2. Sometimes, we create an application server program which sits on the
server side and talks with the database server. Doing this, all the client
programs talks with this application server, so increase the scalablity. Is
it scalable in using Web Services or .NET remoting for this purpose?
3. Any application server framework can be recommended in .NET 2.0?
Benson.
Michael Nemtsev - 23 Jan 2007 09:18 GMT
Hello Benson,
B> Question:
B> 1. Can we say .NET 2.0 framework is an application server layer?
Nope. framework is the framework. it's the platworm to build your apps.
B> 2. Sometimes, we create an application server program which sits on
B> the server side and talks with the database server. Doing this, all the
B> client programs talks with this application server, so increase the
B> scalablity. Is it scalable in using Web Services or .NET remoting for
this purpose?
What are u describing is the DAL - data access layer.
The better way is to use WCF, if net - than to WS or Enterprise Services
(COM+)
.NET is not very good from the declarativeness perspective.
B> 3. Any application server framework can be recommended in .NET 2.0?
BizTalk :) But it's very huge and I don't think it's exactly what u need.
Everything you need to build is the small set of services which provide the
necessary functionality on server. For these reasons windows COM+ - the set
of services.
I suppose it's the right way for your, depending on your functionality
---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangel