Web services VS COM+ Services

[kumaran]

Hi,

For our application, we want to develop some .Net Components which act as
a middle tier.

These components should be explored as web services in the later phases of
the development.

So we plan to develop these components as web services. I want a clear pros
and cons of developing these compoents as web services or having it as a
.Net Components wrapped with COM+ Services.

If they are web services, how abt using COM+ Services.. This is my issue.

I hope u have understood my problem.

Kumaran

[Christian Weyer]

You already know my opinion ;-)

Christian
---------------------------------
.NET XML Web Services Repertory
http://www.xmlwebservices.cc/
---------------------------------

kumaran wrote:
> Hi,
>
> For our application, we want to develop some .Net Components which act as
> a middle tier.
>
> These components should be explored as web services in the later phases of
> the development.
>
> So we plan to develop these components as web services. I want a clear pros
> and cons of developing these compoents as web services or having it as a
> Net Components wrapped with COM+ Services.
>
> If they are web services, how abt using COM+ Services.. This is my issue.
>
> I hope u have understood my problem.
>
> Kumaran
>

[Lee]

Web services can be called via http, so therefore you will have less issues
if you communicate to your object through a firewall. Also, useing webservices,
your objects are much more portalble from other systems. This is because
the interface communication is based industry stadard. (XML & SOAP) For
futureproofing your architecture, use Webservices.

COM+ has the advantage of transaction handling. With a webservice you should
do the entire transaction in one go, or write your own two phase commit algorithm.

Hope this helps.

Christian Weyer <cw@no-spam-xmlwebservices.cc> wrote:
>You already know my opinion ;-)
>
>Christian
>---------------------------------
> .NET XML Web Services Repertory
> http://www.xmlwebservices.cc/
>---------------------------------
>
>kumaran wrote:
>> Hi,
>>
>> For our application, we want to develop some .Net Components which act
as
>> a middle tier.
>>
>> These components should be explored as web services in the later phases
of
>> the development.
>>
>> So we plan to develop these components as web services. I want a clear
pros
>> and cons of developing these compoents as web services or having it as
a
>> Net Components wrapped with COM+ Services.
>>
>> If they are web services, how abt using COM+ Services.. This is my issue.
>>
>> I hope u have understood my problem.
>>
>> Kumaran
>>
>

[Kumaran]

Kumaran,

Its very defficult to create a program over .net using old version of languages
like VB or ASP. I recomend as a solution to you is read a lot of thing related
to .NET because it is imposible to create a system using technics. A lot
of thing changed in the .NET including architecture so u need to change ur
skills to .NET. Just forget your old ideas.

"kumaran" <cn.kumaran@digital.com> wrote:
>
>Hi,
>
>For our application, we want to develop some .Net Components which act as
>a middle tier.
>
>These components should be explored as web services in the later phases
of
>the development.
>
>So we plan to develop these components as web services. I want a clear pros
>and cons of developing these compoents as web services or having it as a
>.Net Components wrapped with COM+ Services.
>
>If they are web services, how abt using COM+ Services.. This is my issue.
>
>I hope u have understood my problem.
>
>Kumaran
>
>

[syd]

How 'bout this:

Write the componets and run them in COM+ to start. If you need to expose
there functionality as web services simply add services that call the components.

"kumaran" <cn.kumaran@digital.com> wrote:
>
>Hi,
>
>For our application, we want to develop some .Net Components which act as
>a middle tier.
>
>These components should be explored as web services in the later phases
of
>the development.
>
>So we plan to develop these components as web services. I want a clear pros
>and cons of developing these compoents as web services or having it as a
>.Net Components wrapped with COM+ Services.
>
>If they are web services, how abt using COM+ Services.. This is my issue.
>
>I hope u have understood my problem.
>
>Kumaran
>
>

[Herman]

COM+ in .Net also known as ServicedComponent.
Communication/Remoting your object (in ServicedComponent) can be through
tcp or http (SOAP). I think COM+ still needed in building enterprise application
(Transaction, Pool, Queue)

Herman.


"Lee" <Lee@NoEmail.com> wrote:
>
>Web services can be called via http, so therefore you will have less issues
>if you communicate to your object through a firewall. Also, useing webservices,
>your objects are much more portalble from other systems. This is because
>the interface communication is based industry stadard. (XML & SOAP) For
>futureproofing your architecture, use Webservices.
>
>COM+ has the advantage of transaction handling. With a webservice you should
>do the entire transaction in one go, or write your own two phase commit
algorithm.
>
>Hope this helps.
>
>Christian Weyer <cw@no-spam-xmlwebservices.cc> wrote:
>>You already know my opinion ;-)
>>
>>Christian
>>---------------------------------
>> .NET XML Web Services Repertory
>> http://www.xmlwebservices.cc/
>>---------------------------------
>>
>>kumaran wrote:
>>> Hi,
>>>
>>> For our application, we want to develop some .Net Components which act
>as
>>> a middle tier.
>>>
>>> These components should be explored as web services in the later phases
>of
>>> the development.
>>>
>>> So we plan to develop these components as web services. I want a clear
>pros
>>> and cons of developing these compoents as web services or having it as
>a
>>> Net Components wrapped with COM+ Services.
>>>
>>> If they are web services, how abt using COM+ Services.. This is my issue.
>>>
>>> I hope u have understood my problem.
>>>
>>> Kumaran
>>>
>>
>