Web Services and COM?

[david]

I was told that XML Web services has replaced /will replace the COM/DCOM.
Anybody could tell me why/how?
If I want to handle the remote image processing and image transfer/display
accessed from either web client or windows application client, is the web
services a good choice for doing it? If so, what is the reason to use it?

Thanks

Davud

[Craig Deelsnyder]

On Thu, 04 Aug 2005 09:44:08 -0500, david
<da***@discussions.microsoft.com> wrote:

I was told that XML Web services has replaced /will replace the COM/DCOM.
Anybody could tell me why/how?
If I want to handle the remote image processing and image
transfer/display
accessed from either web client or windows application client, is the web
services a good choice for doing it? If so, what is the reason to use it?

Thanks

Davud

WebServices are a mechanism that can replace DCOM, though it is a
different architecture of course. They're used mainly for remote
server/application interaction.

Remoting is actually a purer comparison, and usually performs better, as
it is either binary or textual transfer. In fact webservices are a type
of remoting. It's just that remoting is similar to DCOM, in that only
..NET clients can talk via remoting (AFAIK); webservices are supposed to be
more open so other types of clients can interact (a diverse
environment)....

--
Craig Deelsnyder
Microsoft MVP - ASP/ASP.NET

[david]

Thank you for your comments.

It seems that XML web service is very good for text-based communication.
Can it do the communication on binary basis?

If not, how can it replace COM/DCOM?

David

"Craig Deelsnyder" wrote:

On Thu, 04 Aug 2005 09:44:08 -0500, david
<da***@discussions.microsoft.com> wrote:

I was told that XML Web services has replaced /will replace the COM/DCOM.
Anybody could tell me why/how?
If I want to handle the remote image processing and image
transfer/display
accessed from either web client or windows application client, is the web
services a good choice for doing it? If so, what is the reason to use it?

Thanks

Davud

WebServices are a mechanism that can replace DCOM, though it is a
different architecture of course. They're used mainly for remote
server/application interaction.

Remoting is actually a purer comparison, and usually performs better, as
it is either binary or textual transfer. In fact webservices are a type
of remoting. It's just that remoting is similar to DCOM, in that only
..NET clients can talk via remoting (AFAIK); webservices are supposed to be
more open so other types of clients can interact (a diverse
environment)....

--
Craig Deelsnyder
Microsoft MVP - ASP/ASP.NET