Why can an NSConnection only vend objects if sendPort == receivePort?
Why can an NSConnection only vend objects if sendPort == receivePort?
- Subject: Why can an NSConnection only vend objects if sendPort == receivePort?
- From: Wade Tregaskis <email@hidden>
- Date: Thu, 28 Aug 2003 13:47:56 +1000
As the subject says, I'm curious as to why NSConnection's are limited
in this way. It seems to me that it makes a lot of sense to use the
one port for all communications if you're doing sockets over a network,
since you need only resolve any firewall/NAT/etc issues once.
Is it a design issue, or simply an arbitrary limit? Or, is it simply a
case of poor documentation, wherein you can actually have sendPort ==
receivePort and still use the NSConnection fine (for obtaining a vended
object from another host)?
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.