On 13/09/10 18:11, Jani Hakala wrote:
> How about dividing this call from object A to object B to two calls
> to object B? First one would return at that point where B now calls A
> and the second call would give the object B the results of the
> call. Any parameters required by object A could be passed as the
> result from the first call.
Unfortunately, I can't change the IDL, which includes the call from
object A to object B. It is defined by a standard and I must comply with
that standard. Otherwise I would have used a set of one-way calls, just
as I did in the pure Erlang version of the objects.
> AMI/AMH [1] might provide another solution if they are available. Or
> perhaps multiple servants for object A.
>> I prefer to avoid two-way calls with CORBA as much as possible. I
> once tried those with C++ and ACE/TAO, and it seemed to be too much
> trouble. I didn't try AMI/AMH or multiple servants though as I was
> just learning CORBA basics.
I agree; I prefer one-way calls for the same reasons, and particularly
for the reason that lead to this post. It's a good real-life example of
how Erlang has a better RPC system than CORBA.
Geoff