Re: Failure attempting to implement an NSPort subclass for Distributed Objects
Re: Failure attempting to implement an NSPort subclass for Distributed Objects
- Subject: Re: Failure attempting to implement an NSPort subclass for Distributed Objects
- From: Wade Tregaskis <email@hidden>
- Date: Tue, 7 Oct 2003 21:36:18 +1000
My only suspicion at present is that the server NSConnection receives
the message from a port it does recognise, since it comes from the
spawned server port, not the listening server port that was originally
given to it. In this case it seems to be sending a generic empty
reply back on the send port provided to it. But then the client
NSConnection seems to be accepting that, even though it too receives
it from a spawned port from what is it's actual listener port...
Well, I found myself with a couple of free hours unexpectedly, so I
decided to put this to the test. As it turns out, it appears I'm
right! With a bit of tweaking and horrifyingly bad patch code, I have
my listener subport's pose as their parent (i.e. pass their parent
instead of themselves in the NSPortCoder/NSPortMessage), which seems to
be good enough to convince NSConnection to do it's normal thing, and
return valid data!
So, while my port still doesn't quite work - I'll need to rewrite the
code properly now - it appears this is indeed the problem that's been
eating at me for months.
I know I'm probably talking to myself largely here, but it's probably
worth placing this solution into the list archives. Perhaps it will
save future developers from the same fate. :)
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.