• 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
NSData encoding issues...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSData encoding issues...


  • Subject: NSData encoding issues...
  • From: Alex Lock <email@hidden>
  • Date: Tue, 30 Sep 2003 15:50:28 -0400

Hey all,

So I've got a socket problem. Actually it's not so much a socket problem as it is an NSData problem.

I'm working on an app where (unfortunately) the networking protocols are already written/being used...

All communication (in existing versions) is handled by directly writing characters to the socket, as in:

send (socketfd, &charbuf, length, 0);
recv (socketfd, &charbuf, length, 0);

Where the character buffers are regular (unterminated) C strings. For a new-line delimeter, it uses unsigned char 0xFF (int 255).

Here's the problem... I've tried OmniNetworking, SmallSockets, and now AsyncSockets (which I like best because it supports delegation exactly the way I would implement it myself); they all offer the same problem, text encoding.

Since all data sent to/received from the server in these classes is encapsulated inside an NSData object, I can't simply reference characters directly as I would if I was using the above (raw) socket functions. I've tried using:

[[NSString alloc] initWithData:[myData dataWithEncoding:[NSString defaultCStringEncoding]]];

To give me a "readable" string from the incoming bytes, but this doesn't seem to work...

I've tried using NSData's getBytes:length: method to copy it into a character buffer (which I could then convert to a cstring and copy into an NSString), still doesn't work...

My question is, if data is being sent/received from the server in the manner outlined above, what is the "proper" way to deal with said data using the NSData object?

Or, am I wasting my time w/ NSData? Is it really necessary for me to write my own socket class just to handle clear-text communication?

Thanks!

Alex <email@hidden>
_______________________________________________
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.

  • Follow-Ups:
    • Re: NSData encoding issues...
      • From: Dustin Voss <email@hidden>
  • Prev by Date: Programatically resizing a NSTableView
  • Next by Date: NSBGOnly, NSUIElement & Co.?
  • Previous by thread: Re: Programatically resizing a NSTableView
  • Next by thread: Re: NSData encoding issues...
  • Index(es):
    • Date
    • Thread