site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Folks. I have an app which communicates to another remote app via a posix socket. Any particular tricks ? pitfalls ? Thanks Mark Gilbert. -- mark@gallery.co.uk Tel: +44 208 340 5677 fax: +44 870 055 7790 http://www.gallery.co.uk New Product ! - MetaCorder Location Sound Field Recorder http://www.metacorder.info _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Previously the communication has been very small messages, up to 10 bytes or so, back and forth. Now one app is requesting a piece of larger data from the other app (30k Bytes), and I have noticed that the communication is a less smooth. In particular, whereas previously I could read 1 byte blocking, then continue reading until 'read' returned-1 (which would be the end of the reply), I now see a return of -1 part way through the 30k reply, and it picks up again later. Before I rework this code to deal with this, I wanted to get any general guidelines on the best way to handle exchange of larger packets of data via sockets. This email sent to site_archiver@lists.apple.com