WebServices / Com+

[Keith Hurst]

Hi,

this is my first post to this group, so please be gentle with me.

We have a classic Win32 application and are now transporting that to browser
based using VS.NET. Another steep learning curve to get to grips with.

3 Tier - Presentation Layer, Business Logic Layer, Data Server Layer.

In the Business Logic Layer a colleague of mine is proposing that we access
the data through a WebService which in turn calls function(s) in a COM+
module which in turn actually accesses the DS Layer. I personally do not see
why we have to go through he COM+ route, it seems like another stepping
stone which is not needed. I think we should just be able to access the DS
Layer from the WebService and return the desired result.

Am I missing something here, which is the best way in your opinion. Any web
links for research ?

Kind Regards
Keith Hurst

[Anders Norås [MCAD]]

Keith Hurst wrote:

In the Business Logic Layer a colleague of mine is proposing that we access
the data through a WebService which in turn calls function(s) in a COM+
module which in turn actually accesses the DS Layer. I personally do not see
why we have to go through he COM+ route, it seems like another stepping
stone which is not needed. I think we should just be able to access the DS
Layer from the WebService and return the desired result.

If you need any of the COM+ services such as distributed transactions or
queued components you can benefit from using COM+ Enterprise Services.
If you only need to do regular CRUD operations on a database there is no
real need for COM+.

There is lots of information on .NET application architecture
best-practies on Microsoft's Patterns & Practices Center:
http://www.microsoft.com/resources/p...s/default.mspx

I'd particulary recomend the .NET Data Access Architecture Guide:
http://msdn.microsoft.com/library/de.../html/daag.asp
and Application Architecture for .NET: Designing Applications and
Services:
http://msdn.microsoft.com/library/de...asp?frame=true
for further information on the topic in question.

Anders Norås
http://dotnetjunkies.com/weblog/anoras/

[Dilip Krishnan]

Hello Keith,
You're right in the fact that its going to add another layer to into
the mix. Some things to consider are tho' Webservices are great and solve
a great many problems, they are in general not as performant as a non-distributed
tiered application; This is because of the overhead of serialization and
deserialization; So if this is a real time application, WS may not be a desirable
solution. Secondly, having COM+ in the mix makes it even less performant
because of the overhead of com interop. Just my thoughts

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com

Hi,

this is my first post to this group, so please be gentle with me.

We have a classic Win32 application and are now transporting that to
browser based using VS.NET. Another steep learning curve to get to
grips with.

3 Tier - Presentation Layer, Business Logic Layer, Data Server Layer.

In the Business Logic Layer a colleague of mine is proposing that we
access the data through a WebService which in turn calls function(s)
in a COM+ module which in turn actually accesses the DS Layer. I
personally do not see why we have to go through he COM+ route, it
seems like another stepping stone which is not needed. I think we
should just be able to access the DS Layer from the WebService and
return the desired result.

Am I missing something here, which is the best way in your opinion.
Any web links for research ?

Kind Regards
Keith Hurst

[Keith Hurst]

Cheers Dudes,

obviously lots of reading afoot.

Regards
Keith Hurst

"Dilip Krishnan" <dk*******@NOSPAM.geniant.com> wrote in message
news:15**********************@msnews.microsoft.com ...

Hello Keith,
You're right in the fact that its going to add another layer to into
the mix. Some things to consider are tho' Webservices are great and solve
a great many problems, they are in general not as performant as a non-distributed tiered application; This is because of the overhead of serialization and
deserialization; So if this is a real time application, WS may not be a desirable solution. Secondly, having COM+ in the mix makes it even less performant
because of the overhead of com interop. Just my thoughts

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com

Hi,

this is my first post to this group, so please be gentle with me.

We have a classic Win32 application and are now transporting that to
browser based using VS.NET. Another steep learning curve to get to
grips with.

3 Tier - Presentation Layer, Business Logic Layer, Data Server Layer.

In the Business Logic Layer a colleague of mine is proposing that we
access the data through a WebService which in turn calls function(s)
in a COM+ module which in turn actually accesses the DS Layer. I
personally do not see why we have to go through he COM+ route, it
seems like another stepping stone which is not needed. I think we
should just be able to access the DS Layer from the WebService and
return the desired result.

Am I missing something here, which is the best way in your opinion.
Any web links for research ?

Kind Regards
Keith Hurst