Re: DO Proxy
Re: DO Proxy
- Subject: Re: DO Proxy
- From: Timothy Ritchey <email@hidden>
- Date: Tue, 14 May 2002 08:35:52 -0500
Is this last proxy a proxy to C's proxy to A, if you
understand what I mean ;)?
Forgot to comment on this. My assumption is that the proxy in A is
simply a loopback. When I pass X back from C to A, I can see another
connection being created - two actually. At first this didn't make sense
to me, but now it suddenly does. I bet if I look at those two new
connections, one will have a single local object - X and the other will
have a single remote object - the proxy to X. When I do an [NSString
stringWithFormat:@"%@", X] on the original object, and the proxy, I get:
original: ComponentA <0x1d5370>
proxy: ComponentA <0x1d5370>
or some such, so they are certainly pointing to the same thing. But the
object I get from C returns YES on [component isProxy]
A question for the audience. I have had to resort to using more
circumstantial evidence for my conclusions, as I can't seem to figure
out a definitive method for determining where the end of a connection
goes. How do I determine which process/thread, etc. the other end of a
connection is connected to? I want to be able to dump some kind of info
in the following while loop that will allow me to track it down:
NSEnumerator *e = [[NSConnection allConnections] objectEnumerator];
NSConnection *connection;
while(connection = [e nextObject]) {
// check to see where the other end is going
}
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| References: | |
| | >Re: DO Proxy (From: Timothy Ritchey <email@hidden>) |