Understanding DO internals
Understanding DO internals
- Subject: Understanding DO internals
- From: Wade Tregaskis <email@hidden>
- Date: Thu, 21 Aug 2003 20:55:51 +1000
There's two parts to this - the first is a plea for anyone with
extensive DO knowledge (particularly with regards to implementing
custom subclasses of NSPort) to drop me a line so I can pick their
brains a bit. :)
The second is a more direct question on the same topic - after creating
an NSConnection using only a sendPort, I see an instance of my custom
NSPort-subclass instantiated. This is done using the default 'init'
method, which I've rigged up to create a "default" listening port for
NSConnection's convenience (I don't use this method myself). This port
is then told by the NSConnection [or some other class that's not mine]
to add itself to the runloop in both normal and "NSConnection waiting
for reply" mode... then it's released. 'isValid' is never called, and
everything goes smoothly, so I don't see that this is a result of the
port being rejected - it seems that the NSConnection is creating a port
with no intention of keeping/using it. Anyone have any ideas what's
going on here?
Also, two other ports I create manually are not told to add/remove
themselves from any runloops, when adopted by NSConnection's... should
I be doing this myself? At present my port attaches to the default
runloop when it's created, but this might be a problem with multiple
threads, where the NSConnection is created in a separate thread to the
port(s) it uses.
Wade Tregaskis
-- Sed quis custodiet ipsos custodes?
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.