|
![](/i/fill.gif) |
Orchid XP v8 <voi### [at] dev null> wrote:
> > Think of it like a procedure call between machines. :-)
> Normally prorams can't call functions in other programs. (Unless you
> count the operatin system.) And certainly not in programs runnin on
> another machine.
In many object-oriented languages, such as for example objective-C,
dynamic binding is done with a messaging system. In other words, when
you want to call the member function of an object (even if you don't
know the exact type of that object, but only have an abstract handle
to it), what happens internally is that a "message" is sent at runtime
to that object, and the object can accept it (in practice by the object's
type implementing the proper member function) or not. In practice this is
very much like a member function call (except that you don't necessarily
need to know that the object supports that function call).
It's perfectly possible to send these messages between procedures, and
I assume even if these procedures are running in different computers. So
basically it ends up being one program calling the member function of an
object in another program (possibly running on a different computer).
Here's some documentation about remote messaging in objective-C:
http://tinyurl.com/9339sk
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |