|
From: | MJ Ray |
Subject: | Re: AW: D-BUS versus GDOMAP (Was: D-BUS equivalent) |
Date: | Tue, 31 Aug 2004 12:36:10 +0100 |
On 31 Aug 2004, at 11:08, MJ Ray wrote:I think that's a little unfair ... as the design/rationale is documented near the front of gdomap.hThat's not very helpful. It ranks alongside "STFW" and "RTFM".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.
Its purpose is solely to map service names to ports on a network-wide basis. [...]
That's a clearer description than the man page currently has. Can you or another copyright assigner add it there, please?
Not that | know of ... I'm not sure what you would want in an 'example' anyway. [...]Is there an example of a GDO conversation somewhere?
Pretty much what you described. I'm sort of used to reading RFCs and a lot of their protocol ones include examples, which are bascially "here are a couple of typical conversations for this protocol". They really do help a lot.
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.
-- MJR/slef My Opinion Only and not of any group I know http://www.ttllp.co.uk/ for creative copyleft computing Please email about: BT alternative for line rental+DSL; Education on SMEs+EU FP6; office filing that works fast
[Prev in Thread] | Current Thread | [Next in Thread] |