• 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
Best practice for large packets
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Best practice for large packets


  • Subject: Best practice for large packets
  • From: Jonathon Kuo <email@hidden>
  • Date: Tue, 18 Jan 2011 08:07:12 -0800

In sending/receiving large packets over TCP, I've noticed that if I try to use packets larger than 90k on our WAN, or packets larger than 146k on our LAN, the reads and writes will timeout.
  read(): Operation timed out

So I'm thinking that this is why IOVs were created. Before I go through all the hassle to reimplement everything using reav() and writev(), is this the right approach? Is there a #DEFINE or known "safe" size for each vector - 10k? 50k?

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: [CFSocket] When should a CFSocketRef be invalidated?
  • Next by Date: [CFSocket] Invalidating a CFSocketRef revisited
  • Previous by thread: Re: [CFSocket] When should a CFSocketRef be invalidated?
  • Next by thread: [CFSocket] Invalidating a CFSocketRef revisited
  • Index(es):
    • Date
    • Thread