[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AW: D-BUS versus GDOMAP (Was: D-BUS equivalent)

From: Richard Frith-Macdonald
Subject: Re: AW: D-BUS versus GDOMAP (Was: D-BUS equivalent)
Date: Tue, 31 Aug 2004 18:35:40 +0100

On 31 Aug 2004, at 12:36, MJ Ray wrote:

On 2004-08-31 11:38:30 +0100 Richard Frith-Macdonald <address@hidden> wrote:

On 31 Aug 2004, at 11:08, MJ Ray wrote:
That's not very helpful. It ranks alongside "STFW" and "RTFM".
I think that's a little unfair ... as the design/rationale is documented near the front of gdomap.h
His email may have been very terse, but it *was* accurate [...]

Accurate but about as incomplete as humanly possible, rather like answering a hungry man who asks "where can I find food?" with "on a farm". Even pointing to gdomap.h would have been better. I think I'd already looked through the source a bit by that point and found little helpful in it. I'm not used to .h files containing more than the man pages or class docs.

I think it's quite common ... but I guess it depends on your background.

The distributed objects mechanism is described reasonably in the NeXT documentation and also in the class documentation, though an overview really has to be inferred from the class documentation.

Which NeXT documentation and which classes deal with this? I already didn't find it in the OpenStep specification, although some pages seem to be missing from the copy I'm using.

NEXTSTEP general reference volume2 chapter6 (not sure if/where it's available online).
The core classes are NSPort, NSConnection.
Other more recently exposed/documented classes are NSDistantObject, NSPortCoder, NSPortNameServer, NSSocketPort, NSMessagePort

reply via email to

[Prev in Thread] Current Thread [Next in Thread]