Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6655733
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T01:33:24+00:00 2026-05-26T01:33:24+00:00

This may be an easy one. I’m using GCDAsyncSocket to receive a variable amount

  • 0

This may be an easy one. I’m using GCDAsyncSocket to receive a variable amount of bytes representing discrete data chunks from a server which appear in a NSMutableData object.

If the data were words it might look like this:

ChunkChunkChunkChu

nkChunkChunkChunkCh

So after processing three chunks, a partial chunk "Chu" remains and has to be retained so that the next lot of data can compete that chunk.

Right now the processing flow looks like this:

receive data, appending to myBuffer
process contents of buffer up to last complete chunk
create new myBuffer with partial fragment of remaining data chunk at end of buffer
back to the start

This works well but I’m not sure if it is the most efficient way. I see that NSMutableData has a replaceBytesInRange that I could use to remove a count of processed bytes from the buffer’s start but it is reportedly a slow operation.

Any suggestions on the best way to do this? If it makes a difference I am using ARC so I expect the overhead of creating/freeing is reduced.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T01:33:24+00:00Added an answer on May 26, 2026 at 1:33 am

    I think Mecki got it wrong in the post you linked to. The more data you remove, the faster it will be, since there are fewer bytes that need to be copied. Also, since you are simply moving the data from the end to the beginning and changing the length, it should be faster than creating a new buffer, since you only have to copy the bytes instead of creating a buffer, copying the bytes, and destroying the old buffer.

    Using your example, the first set of data is ChunkChunkChunkChu. This is 18 bytes long, and you want to keep the last 3. Using replaceBytesInRange:withBytes:length:, the operation looks like this:

    1. Use the full chunks. After this, length is 18 and numLeft is 3.
    2. Call [buffer replaceBytesInRange:(NSRange){0,length-numLeft} withBytes:nil length:0];
      a. Copy 3 bytes from position 15 to position 0.
      b. Set the length to 3.
    3. Receive more data.

    By creating a new buffer, the operation looks like this.

    1. Use the full chunks. After this, length is 18 and numLeft is 3.
    2. Allocate a new buffer.
    3. Append the remaining bytes to the new buffer.
      a. Copy 3 bytes from position 15 of the old buffer to position 0 of the new buffer.
      b. The length of the new buffer is now 3.
    4. Deallocate the old buffer.
    5. Receive more data.

    As you can see, the operation is exactly the same, except that the second has the overhead of creating a new buffer and destroying the old one.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

This may be an easy one. I looked through previous questions (and other places
I am coming from MSSQL, and now using Mysql, this may be a easy
This may be an easy question, but if it is one i haven't found
I am fairly new to OSX development, so this may be easy but google
This may be super easy to solve but I can't find the correct google
This may seem an easy question, but not to me, also a search has
I may be missing something here because I thought this might be really easy
This may be simple one, but 5 mins of Googling didn't give me the
Hey everyone. I'm not big into UI programming so this may be an easy
Hopefully this will be an easy one to answer. I created a class in

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.