• 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
Re: NSPipe (NSFileHandle) writedata limit?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSPipe (NSFileHandle) writedata limit?


  • Subject: Re: NSPipe (NSFileHandle) writedata limit?
  • From: Jens Alfke <email@hidden>
  • Date: Mon, 12 Apr 2010 09:24:04 -0700

On Apr 12, 2010, at 9:09 AM, Greg Guerin wrote:

> You must send the notification with size and such BEFORE writing to the pipe.  Otherwise the sender can become blocked, because the receiver doesn't know it should be reading anything.

And it seems strange to use a second mechanism (a distributed notification) to tell the receiver that data is available. You don’t really need this — the reader can just wait for the NSStreamEventHasBytesAvailable event and then read the data. Then you can send everything over a single stream.

—Jens_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >Re: NSPipe (NSFileHandle) writedata limit? (From: Greg Guerin <email@hidden>)

  • Prev by Date: Re: IKImageView delegate
  • Next by Date: Re: Data managment
  • Previous by thread: Re: NSPipe (NSFileHandle) writedata limit?
  • Next by thread: Re: NSPipe (NSFileHandle) writedata limit?
  • Index(es):
    • Date
    • Thread