• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
NSSocketPort bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSSocketPort bug?


  • Subject: NSSocketPort bug?
  • From: Malte <email@hidden>
  • Date: Wed, 15 Dec 2004 11:30:44 +0100

This is a kind of follow up to the thread i've started earlier asking for help in the BSD <--> Cocoa Socket thing.
I narrowed something down that looks to me like a bug, but maybe i'm just doing something wrong.
Please give me some feedback on this:

When i call:
NSSocketPort * sockPort = [[NSSocketPort alloc] initWithTCPPort:12345];
int socketFD = [sockPort socket];
NSLog(@"server socketFD: %i", socketFD);
The NSLog message gives me a positive integer (i.e. 8 in this case) just like a fileDescriptor should be

However, when i substitute the above with this:
NSSocketPort * sockPort = [[NSSocketPort alloc] initRemoteWithTCPPort:12345 host:@"192.168.1.1"];
int socketFD = [sockPort socket];
NSLog(@"server socketFD: %i", socketFD);
The socketFD is *ALWAYS* == -1 !!

Can anyone verify this? Is this a bug or am i just doing something horribly wrong?

Thanks!

-malte

Attachment: PGP.sig
Description: This is a digitally signed message part

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: NSSocketPort bug?
      • From: Douglas Davidson <email@hidden>
    • Re: NSSocketPort bug?
      • From: João Pavão <email@hidden>
  • Prev by Date: Sending NSString to NSThread task
  • Next by Date: Re: Sending NSString to NSThread task
  • Previous by thread: Re: Sending NSString to NSThread task
  • Next by thread: Re: NSSocketPort bug?
  • Index(es):
    • Date
    • Thread