I was only concerned with performance c/w DCOM or COM+ (which past
experience says can be quite slow)  

Remoting is much further than I want to go, I wouldn't write a tcp/ip tool
for a VB6 application to pass data.  I let other people do for me as this
distract me from what I am paid to do (generate business critical systems,
on budget, on time yada yada yada yawn.)


-----Original Message-----
From: BBallard@A... [mailto:BBallard@A...]
Sent: 13 June 2002 17:36
To: pro_VB_dotnet
Subject: [pro_vb_dotnet] RE: Web Services vs COM+


If you are worried about performance you should take a look at Remoting.
The major draw back I see to Remoting is that you have to write a listen for
each object (unless you use IIS to serve up the remote objects).  Remoting
is very fast and scalable on a pure Windows environment.  Development is
slightly more difficult than using a Web Service, but performance is much
greater.

As for datasets, if you are creating a true stateless n-tier applications,
dataset can not be beat.  They are disconnected by design so they are easy
to pass between tiers, but there is overhead.  There are XML internally so
they are easy to persist to disk and they also have a good scheme for
handling updates after they are reconnected to the database.

-----Original Message-----
From: Kim, Cardyin [mailto:CKim@s...]
Sent: Thursday, June 13, 2002 11:27 AM
To: pro_VB_dotnet
Subject: [pro_vb_dotnet] RE: Web Services vs COM+


The only one that I see is that datasets are using XML.
Although this is quite a breakthrough in the area of
interoperability and stability in your code, you
must realize that transforming any dataset/recordset
to XML will actually bloat the size of the data
a bit (to include all the text tags and schema
descriptors and such).

As long as you avoid trying to work with large
datasets in memory, the benefit that you gain
from using .NET should clearly outweigh
this disadvantage.

Anyone else have any opinions?

Cardyin

-----------------------------------------
Cardyin Kim
Client/Server and Web Development Analyst
San Antonio Community Hospital
Upland, California
ckim@s...        (xxx) xxx-xxxx
-----------------------------------------


-----Original Message-----
From: R MALY GBIPS MIS [mailto:maly@m...]
Sent: Thursday, June 13, 2002 12:20 AM
To: pro_VB_dotnet
Subject: [pro_vb_dotnet] RE: Web Services vs COM+


I am only concerned with communication across a windows only network at the
moment anyhow, you know how businesses change their mind!.  Which made my
immediate response to go with the traditional COM+ architecture,  however
after creating a web service for an asp page and then creating a windows
form that used the same object life seemed to easy!  Are there any drawbacks
(performance or otherwise) to using a web service?

-----Original Message-----
From: Kim, Cardyin [mailto:CKim@s...]
Sent: 12 June 2002 18:37
To: pro_VB_dotnet
Subject: [pro_vb_dotnet] RE: Web Services vs COM+


Some of the well standard marketing reasons are as follows:

1) Web Services can be written to be platform independent,
	where COM+ is generally a Microsoft only technology.

  -This means that if you have a business partner or other
     internal system that wants data from your program, but
     does not use Microsoft technology, a web service
     would allow this much more easily, than a COM+
     component can.

2) You can send data through a firewall.

  -Generally COM+ components cannot work through firewalls 
     unless they have been opened to allow binary type 
     calls.  Usually doing this opens your network up to 
     all kinds of attacks, and is not done in general practice.

3) Web Services use self describing data (XML), COM+ generally
      do not.

  -COM+ uses a binary interface method to transfer calls and
      data.  This means that generally if your COM+ interface
      changes, you may have problems with compatibility with
      programs that already use that component.
      If you use XML, you can avoid this problem since the
      data is text and the schema is self describing.  This
      means that if you add a field to the output of a web
      service, your programs will still continue to function.

There are many other reasons out there, but these a a few
of the major ones.  Hope this helps.

Cardyin

-----------------------------------------
Cardyin Kim
Client/Server and Web Development Analyst
San Antonio Community Hospital
Upland, California
ckim@s...        (xxx) xxx-xxxx
-----------------------------------------


-----Original Message-----
From: Richard Maly [mailto:maly@m...]
Sent: Wednesday, June 12, 2002 5:16 AM
To: pro_VB_dotnet
Subject: [pro_vb_dotnet] Web Services vs COM+


I have been looking at the functionality of Web Services against COM+.  If 
you ignore the transactional handling properties of COM+ (as this is not 
important to me.)  What are the advantages/ disadvantages of either 
system.  I am also trying "future proof" the architecture as best is 
possible.

Any comments, suggestions and discussion will be greatly appreciated
Richard
..


..