Board index » delphi » TCP/IP versus COM/DCOM

TCP/IP versus COM/DCOM

Hi,

I have a question about client/server communication in a very thin
client system:

  While I recognize that COM/DCOM is easier to implement from a
  programming perspective, does COM/DCOM impose greater bandwidth
  demands on the network than an "old-fashioned" TCP/IP port
  connection where small packets are transfered?

Morgan Rodwell
Fluor Daniel

 

Re:TCP/IP versus COM/DCOM


Morgan,

You will find that more bandwidth is used, but the differences are marginal
once a connection is established.  Requests go to and from the client and
server as packaged data - just as your raw TCP/IP implementation does, but in
COM/DCOM you will have some RPC headers - which aren't that big neither.

Nick.

Quote
Morgan Rodwell <rodwe...@home.com> wrote in message

news:3827ba85.8592310@forums.inprise.com...
Quote
> Hi,

> I have a question about client/server communication in a very thin
> client system:

>   While I recognize that COM/DCOM is easier to implement from a
>   programming perspective, does COM/DCOM impose greater bandwidth
>   demands on the network than an "old-fashioned" TCP/IP port
>   connection where small packets are transfered?

> Morgan Rodwell
> Fluor Daniel

Re:TCP/IP versus COM/DCOM


Quote
On Tue, 9 Nov 1999, Nicholas Robinson wrote:
> You will find that more bandwidth is used, but the differences are marginal
> once a connection is established.  Requests go to and from the client and
> server as packaged data - just as your raw TCP/IP implementation does, but in
> COM/DCOM you will have some RPC headers - which aren't that big neither.

Maybe the bandwith doesn't increase a lot, the time to set up a connection
explodes. Setting up a TCP socket takes milliseconds, a COM connection
seconds.

Also, TCP/IP is portable to whatever platform you imagine, and requires
less server power. So propably TCP is the better option, but requires more
work.

Dani?l Mantione

Other Threads