Hi Kiran,
You keep posting this same query over and over. If you're not getting
any answers (beyond my earlier attempts, which admittedly went
nowhere), it isn't because people didn't see the question; it's
because people don't know the answer.
What you are asking is pretty deep into the internals of Distributed
Objects. I think you're going to have to file a bug report with
Apple, or possibly even open a DTS Technical Support Incident.
You report that creating an NSSocketPort in the more typical manner (-
initWithTCPPort:) avoids the exception, but that "some times [the]
socket is not allocated". What do you mean by that? Does -
initWithTCPPort: return nil? Is anything logged when that happens?
In other words, perhaps solving whatever problem you're seeing with -
initWithTCPPort: is easier than solving the exception you're getting
when using -initWithProtocolFamily:socketType:protocol:socket:.
In any case, taking this issue directly to Apple through the
appropriate channels is the most certain way to get it addressed.
There are plenty of knowledgeable folks on these lists, but perhaps
nobody with the deep technical knowledge necessary to solve your
problem.
Regards,
Ken
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
