Re: Closing Distributed Object connections
Re: Closing Distributed Object connections
- Subject: Re: Closing Distributed Object connections
- From: Wade Tregaskis <email@hidden>
- Date: Thu, 9 Oct 2003 12:39:28 +1000
The problem lies with a server hosting an object, who closes it's
NSConnection's fine, but there are still clients connected to the
server. In this scenario the connection on the same host and port are
rendered useless for the next few minutes.
I'm not sure how you're "closing NSConnection's"... presumably you are
invalidating them? Invalidating an NSConnection should cause it to
invalidate all it's port's immediately. Thus, there should be no delay.
If you're doing this and there is a delay, you might be seeing what I
think is a known bug, in which ports cannot be reused immediately after
being closed. I have not seen this myself however, so it must be
implementation specific. You may be able to work around this by
adjusting the socket parameters... search the list archives for past
posts on the issue.
Wade Tregaskis
-- Sed quis custodiet ipsos custodes?
_______________________________________________
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.