Distributed services?

[tellme]

Just got my first .NET framework course. A framework also developped
by my company. The tech guy got me totally confused:
- The UI talks to the controller
- the Controler talks to the manager
- the manager talks to the Dal factory
- the DAL talk to the Impl proxy
- the Web service talks to the manager or an other web service
- A business object is not a web service
....On top of this nightmare, there is not server for the web service,
the DLL must be copied on every PC running my .NET application...!
Apparently it is to prevent large SOAP messages to go back and forth
on the network?

J2EE is clear, the UI talks to the BO, the BO talks to the DB. There
is a BO server somewhere that everybody talks to, the DB can also be
on a server..etc.

Can someone points me to a document clarifying what is a distributed
service architecture with .NET?

Thanks.

[Cowboy (Gregory A. Beamer) - MVP]

You can build a distributed app that has a UI talking to BO, which talk to
your DAL. It is spreading this across machines that expands the problem, as
each machine must have the objects that are being transported. If you are
transporting data, instead, there is no issue.

NOTE: The same issue is present in Java, if you are going fully OO, as you
have to have object definitions on each server. The most common method of
solving the bigger issue is to compile the objects into a separate assembly
(.NET), etc.
---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

"tellme" wrote:

Just got my first .NET framework course. A framework also developped
by my company. The tech guy got me totally confused:
- The UI talks to the controller
- the Controler talks to the manager
- the manager talks to the Dal factory
- the DAL talk to the Impl proxy
- the Web service talks to the manager or an other web service
- A business object is not a web service
....On top of this nightmare, there is not server for the web service,
the DLL must be copied on every PC running my .NET application...!
Apparently it is to prevent large SOAP messages to go back and forth
on the network?

J2EE is clear, the UI talks to the BO, the BO talks to the DB. There
is a BO server somewhere that everybody talks to, the DB can also be
on a server..etc.

Can someone points me to a document clarifying what is a distributed
service architecture with .NET?

Thanks.

[John Timney \(ASP.NET MVP\)]

..........and webservices usually helps if you can architect that in....

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"Cowboy (Gregory A. Beamer) - MVP" <No************@comcast.netNoSpamM> wrote
in message news:4C**********************************@microsof t.com...

You can build a distributed app that has a UI talking to BO, which talk to
your DAL. It is spreading this across machines that expands the problem, as each machine must have the objects that are being transported. If you are
transporting data, instead, there is no issue.

NOTE: The same issue is present in Java, if you are going fully OO, as you
have to have object definitions on each server. The most common method of
solving the bigger issue is to compile the objects into a separate assembly (.NET), etc.
---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

"tellme" wrote:

Just got my first .NET framework course. A framework also developped
by my company. The tech guy got me totally confused:
- The UI talks to the controller
- the Controler talks to the manager
- the manager talks to the Dal factory
- the DAL talk to the Impl proxy
- the Web service talks to the manager or an other web service
- A business object is not a web service
....On top of this nightmare, there is not server for the web service,
the DLL must be copied on every PC running my .NET application...!
Apparently it is to prevent large SOAP messages to go back and forth
on the network?

J2EE is clear, the UI talks to the BO, the BO talks to the DB. There
is a BO server somewhere that everybody talks to, the DB can also be
on a server..etc.

Can someone points me to a document clarifying what is a distributed
service architecture with .NET?

Thanks.