Is HX_IOV_MAX a compile time constant or can you alter it via a socket 
option? This isn't really a concern for the client. I'm just curious.

I agree with your other email. I don't really see a use/need for buffering 
UDP since it is unreliable.

"If writes are not currently blocked,an immediate write will be performed 
when either the current write array has HX_MAX_IOV elements filled or the 
current write array contains at least MSS
bytes."

What if the user stops (or pauses) writing before this condition is met? Is 
it possible this will lead to a case where data might end up being held 
indefinitely? (I believe nagle for example will send once all outstanding 
data is acknowledged if there data in the outgoing buffer does not exceed 
the MSS.)

Liam



At 05:39 PM 9/23/2004, Tom Marshall wrote:
>The socket write buffer needs rewritten.  Please see attached for
>motivations and proposed implementation.
>
>--
>One of the saddest lessons of history is this:  If we've been bamboozled
>long enough, we tend to reject any evidence of the bamboozle.  We're no
>longer interested in finding out the truth.
>         -- Carl Sagan, "The Fine Art of Baloney Detection"
>
>
>_______________________________________________
>Common-dev mailing list
>Common-dev at lists.helixcommunity.org
>http://lists.helixcommunity.org/mailman/listinfo/common-dev