• 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
Recommended API for two-way transfers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Recommended API for two-way transfers


  • Subject: Recommended API for two-way transfers
  • From: Chris Silverberg <email@hidden>
  • Date: Mon, 04 Feb 2002 10:33:54 -0800
  • Organization: Aladdin Systems, Inc.

I'd like to get anyone's opinion on the following...

I have an application that establishes up to four TCP connections with
remote clients. On each connection a continuous amount of data is
transferring in BOTH directions as fast as possible. Think of it as file
transfers going in both directions.

Currently this is achieved using async OT w/ cooperative threading. This
works, but it makes the application extremely sluggish and consumes way too
much CPU. (And it's probably getting poor performance since it spends so
much time switching cooperative threads).

So, I'm trying to figure out what my options are. OTMP is definitely a
possibility since it gives me backwards compatibility with MacOS 9. But I'm
open to going MacOS X only. So bsd sockets, CFSocket, or anything else are
on the table.

The key to figuring out which model works best, is the fact that I need to
transmit and receive data simultaneously. This is not request/response type
of protocol.

Any advice is greatly appreciated.

thanks,
Chris


  • Follow-Ups:
    • Re: Recommended API for two-way transfers
      • From: Becky Willrich <email@hidden>
References: 
 >Network Programming Models (was OTCountFreeBytes?) (From: Quinn <email@hidden>)

  • Prev by Date: Re: Network Programming Models
  • Next by Date: Re: Threads vs Select (was Re: Re(2): [Repost] OTCountFreeBytes? (like OTCountDataBytes but for send))
  • Previous by thread: Re: Network Programming Models
  • Next by thread: Re: Recommended API for two-way transfers
  • Index(es):
    • Date
    • Thread