diff options
author | stoddard <stoddard@13f79535-47bb-0310-9956-ffa450edef68> | 2000-08-18 18:29:39 +0000 |
---|---|---|
committer | stoddard <stoddard@13f79535-47bb-0310-9956-ffa450edef68> | 2000-08-18 18:29:39 +0000 |
commit | 1210438dc8c1fe55ae28610b039572b1bdd2319a (patch) | |
tree | 4ddc521af7c1288a6716552a61009163b162c6d5 /i18n/unix | |
parent | d09f6c640d6f156d9d494e7322eb569a233b64bb (diff) | |
download | libapr-1210438dc8c1fe55ae28610b039572b1bdd2319a.tar.gz |
Win32: After much experimentation, I've decided to continue to use
setsockopt(SO_SNDRCVTIMEO). Applications will need to segment apr_sends
or set timeouts appropriately to accomodate slow clients.
Apache should be fine as it does not typically attempt to apr_send more
than 8192 bytes at once with default timeouts of 15 seconds.
apr_sendfile() is another matter... On Windows, TransmitFile will block
(or not trigger a completion event) until the entire file content is sent.
It is easy for a slow client to request a file than cannot be served before
the timeout expires. To accomodate these cases, I introduced the
MAX_SEGMENT_SIZE #define to define the maximum amount of data TransmitFile
will be asked to send at once. The default setting of 65536 should accomodate
most clients dialed in at 28K (or more) if i/o timeouts are configured
to be 30 seconds or more.
git-svn-id: http://svn.apache.org/repos/asf/apr/apr/trunk@60506 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'i18n/unix')
0 files changed, 0 insertions, 0 deletions