This is the case with DCOM and I suspect with CORBA as well. The suggested
way is to minimize the number of calls to the remote object by making method
calls where you pass all the property values as a list of parameters.
So in stead of:
O = CreateRemoteObject(...)
O.ID = 2
O.Name = "John"
O.Tel = "1234567"
You should do:
O = CreateRemoteObject(...)
O.SetProperties(2, "John", "1234567")
Another way (just thinking as I'm going) is to pass all the property names
and values as an XML fragment (i.e. needing only one parameter of type
string). This will allow expanding in future without breaking the contract
interface:
O.SetProperties("<Properties><ID>2</ID><Name>John</Name><Tel>1234567</Tel></
Properties>")
HTH
Xander
----- Original Message -----
From: Peter G Jones <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Sent: Tuesday, February 15, 2000 5:37 AM
Subject: [DUG]: Marhsalling: COM vs Corba
> Imageine I have a server process that creates a object and returns the
> interface to the client. With COM, if I call methods and set properties
on
> this instance I get network traffic cause the object is alive on the
server,
> not the client. Correct ?
>
> With Corba (or COM), is there a way of avoiding this network traffic? IE,
> can the object be magically transported to the client rather than just a
> reference to it?
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
>
> --------------------------------------------------------------------------
-
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
