newbie

Hi,

The application which I am working on uses the proxy & facade patterns to
access data from sql server 2005. The proxy accesses the service.


It uses some kind of remoting service to access the business layer. This service
needs to be started from ComputerManagement -> Services. What is remoting
here and why do we use it? Can you help me with that. Some good examples can
help. 


Thanks.

ppayal:What is remoting here and why do we use it?  

.NET remoting is just a means to allow communication between .NET applications
that reside in different application domains. This means you can have 2 .NET
applications talking over 2 different machines using an agreed channel and
format like TCP/HTTP and XML/Binary.

In a way it is doing the same thing as web services are but a different
implementation.

http://msdn2.microsoft.com/en-us/library/kwdt6w2k(VS.71).aspx

http://www.developer.com/net/cplus/article.php/1479761

Is this Service Oriented architecture?

I have two projects: User Interface layer and busines logic layer. The user
interface accesses the business logic through a windows service. What benefit is
it to access it via a windows service? Is this service oriented architecture?

"ppayal" wrote in message news:2253651@forums.asp.net...

 I have two projects: User Interface layer and busines logic layer. The user
interface accesses the business logic through a windows service. What benefit is
it to access it via a windows service? Is this service oriented architecture?

http://forums.asp.net/p/1236757/2253651.aspx#2253651

Hosting the business logic in a service (on a remote machine) allows reuse and
centralization of the logic to multiple clients. So you could, for instance,
reuse the logic across both a Windows Forms UI, a Web Forms UI, and a WPF UI. If
it's all on the same machine, it's of dubious benefit...unless you just enjoy
making things slower than they need to be. ;) Is this SOA? Maybe...it depends on
the external interface of your service and what it does. You could implement SOA
using Windows services with Remoting, SOAP, etc. (or some other transport), but
having remote callable services doesn't necessarily give you SOA (it does,
however, give you 1 more tier in the n-tier). SOA is more design philosphy, less
implementation or technology details.  My 1 sentence definition of SOA (which,
BTW, nobody agrees with me on...but, then again, nobody agrees with anybody on a
SOA definition) is something along the lines of "a bunch of coarsely
interfaced, remotely callable, services that perform defined *business*
processes".  --MB