Re: NSDistantObjectRequest

[Jay McCarthy]

On Sun, 2001-12-09 at 01:33, Richard Frith-Macdonald wrote:
[snip]
> > Is there a problem with implementing this class inherent in GNUstep or
> > has it just merely been forgotten?
> 
> The reason that the class is not implemented is that there is nothing
> I've yet found on MacOS-X to say what it should do or why it is
> necessary.  In fact the only documentation I have found on it on the
> apple site says explicitly that you should not need to use it.

Ya, I got that from the apple documentation as well - it is extremely
vague. The only thing that I could gather about what it MIGHT do is be
something like:
@implementation NSDistantObjectRequest
 NSConnection *connection;
 NSInvocation *invocation;
- (NSConnection *)connection {
 return connection;
}
- (id)conversation {
 if ( connection != nil ) {
  return [connection currentConversation];
 } else {
  return nil;
 }
}
- (NSInvocation *)invocation {
 return invocation;
}

I dont see how or why this would be useful, and I dont understand how
replyWithException would be implemented.
The code that I am porting uses it in a subclass of NSDistantObject ( i
think, i am not at the office with that code so I can't check), in such
a way that it looks like it just needs the replyWithException to tell
the distant object that it is asking for a method (or object) that does
not exist. (it's in the else of a test for nil)

I know I probably seem like a jerk when I ask about these unimplemented
things, but my ignorance about the world of objective-c and OPENSTEP put
me in a position where I dont necessarily understand the code I am
porting. I apologize for this.

--
Jay McCarthy <jay@kenyamountain>