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: Thu, 9 Oct 2003 00:11:17 +1000
Yet another chapter to add to this saga. At least progress is being
made now.
I've finally got the thing "working". The problem now is that it only
works if I provide protocols for each NSDistantObject, because as soon
as either side sends a methodDescriptionForSelector: request, the reply
comes back fine, but is not handled properly. I dispatch it just the
same way as all other messages & replies, but the side that receives
the reply just sits there doing nothing, until eventually the message
below pops up.
2003-10-08 22:36:09.689 SecureThreads[2577] <NSThread: 0x114dd00>{num
= 2, threadDictionary =
<CFDictionary 0x1225230 [0xa01303fc]>{type = mutable, count = 1,
capacity = 3, pairs = (
2 : HierLog Whitespace = <CFString 0x1151420 [0xa01303fc]>{contents =
" "}
)}
}: tossing reply message sequence 4
So the side that invoked methodDescriptionForSelector: is apparently
timing out waiting for the reply, which as I said does come back, and
is dispatched.
Also, 4 just happens to be the sequence number of the
methodDescriptionForSelector: message/reply pair, although it could
just be coincidence.
Anyway, anyone have any ideas why replies to
methodDescriptionForSelector can't be just dispatched like other
messages/replies?
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.