summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOssama Othman <ossama-othman@users.noreply.github.com>2001-11-15 05:11:51 +0000
committerOssama Othman <ossama-othman@users.noreply.github.com>2001-11-15 05:11:51 +0000
commit7de13d5c330c56e80129120efc15477302e98165 (patch)
treeccab39c332135f262fa5e29de18f09e90843cfd7
parent3f40bd99d9dfc5916d439eb60260710a5079f7eb (diff)
downloadATCD-7de13d5c330c56e80129120efc15477302e98165.tar.gz
*** empty log message ***
-rw-r--r--ChangeLog7
-rw-r--r--ChangeLogs/ChangeLog-02a7
-rw-r--r--ChangeLogs/ChangeLog-03a7
3 files changed, 12 insertions, 9 deletions
diff --git a/ChangeLog b/ChangeLog
index 664efb805b9..88073e81a1f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -43,7 +43,7 @@ Mon Nov 12 11:41:35 2001 Ossama Othman <ossama@uci.edu>
that use loop to send/receive multiple buffers. If data was
sent or received than do not return -1 on error. Instead return
the amount of bytes sent/received. This is necessary to allow
- the caller to keep track of sent or received data.
+ the caller to keep track of sent or received data. [Bug 882]
Sun Nov 11 23:50:00 2001 Craig Rodrigues <crodrigu@bbn.com>
@@ -63,12 +63,13 @@ Sun Nov 11 10:00:56 2001 Ossama Othman <ossama@uci.edu>
iteration then return the amount of bytes sent, not the error.
This extends previous check for EWOULDBLOCK and ETIME. All
errors are now caught. The caller must always know if any data
- was successfully sent.
+ was successfully sent. [Bug 882]
Do not continue on to the next loop iteration if the amount of
data sent was less than the amount data given. This avoids a
subtle problem where "holes" in the data stream would occur if
partial sends of a given buffer in the iovec array occured.
+ [Bug 882]
Sun Nov 11 07:58:07 2001 Ossama Othman <ossama@uci.edu>
@@ -163,7 +164,7 @@ Sat Nov 10 19:27:36 2001 Ossama Othman <ossama@uci.edu>
- If some data was sent on a previous loop iteration then
return the number of bytes successfully sent.
- In both cases, errno is unchanged.
+ In both cases, errno is unchanged. [Bug 882]
Incidentally, this fixes a problem in TAO's SSLIOP pluggable
protocol when sending very large requests. Thanks to Andrew
diff --git a/ChangeLogs/ChangeLog-02a b/ChangeLogs/ChangeLog-02a
index 664efb805b9..88073e81a1f 100644
--- a/ChangeLogs/ChangeLog-02a
+++ b/ChangeLogs/ChangeLog-02a
@@ -43,7 +43,7 @@ Mon Nov 12 11:41:35 2001 Ossama Othman <ossama@uci.edu>
that use loop to send/receive multiple buffers. If data was
sent or received than do not return -1 on error. Instead return
the amount of bytes sent/received. This is necessary to allow
- the caller to keep track of sent or received data.
+ the caller to keep track of sent or received data. [Bug 882]
Sun Nov 11 23:50:00 2001 Craig Rodrigues <crodrigu@bbn.com>
@@ -63,12 +63,13 @@ Sun Nov 11 10:00:56 2001 Ossama Othman <ossama@uci.edu>
iteration then return the amount of bytes sent, not the error.
This extends previous check for EWOULDBLOCK and ETIME. All
errors are now caught. The caller must always know if any data
- was successfully sent.
+ was successfully sent. [Bug 882]
Do not continue on to the next loop iteration if the amount of
data sent was less than the amount data given. This avoids a
subtle problem where "holes" in the data stream would occur if
partial sends of a given buffer in the iovec array occured.
+ [Bug 882]
Sun Nov 11 07:58:07 2001 Ossama Othman <ossama@uci.edu>
@@ -163,7 +164,7 @@ Sat Nov 10 19:27:36 2001 Ossama Othman <ossama@uci.edu>
- If some data was sent on a previous loop iteration then
return the number of bytes successfully sent.
- In both cases, errno is unchanged.
+ In both cases, errno is unchanged. [Bug 882]
Incidentally, this fixes a problem in TAO's SSLIOP pluggable
protocol when sending very large requests. Thanks to Andrew
diff --git a/ChangeLogs/ChangeLog-03a b/ChangeLogs/ChangeLog-03a
index 664efb805b9..88073e81a1f 100644
--- a/ChangeLogs/ChangeLog-03a
+++ b/ChangeLogs/ChangeLog-03a
@@ -43,7 +43,7 @@ Mon Nov 12 11:41:35 2001 Ossama Othman <ossama@uci.edu>
that use loop to send/receive multiple buffers. If data was
sent or received than do not return -1 on error. Instead return
the amount of bytes sent/received. This is necessary to allow
- the caller to keep track of sent or received data.
+ the caller to keep track of sent or received data. [Bug 882]
Sun Nov 11 23:50:00 2001 Craig Rodrigues <crodrigu@bbn.com>
@@ -63,12 +63,13 @@ Sun Nov 11 10:00:56 2001 Ossama Othman <ossama@uci.edu>
iteration then return the amount of bytes sent, not the error.
This extends previous check for EWOULDBLOCK and ETIME. All
errors are now caught. The caller must always know if any data
- was successfully sent.
+ was successfully sent. [Bug 882]
Do not continue on to the next loop iteration if the amount of
data sent was less than the amount data given. This avoids a
subtle problem where "holes" in the data stream would occur if
partial sends of a given buffer in the iovec array occured.
+ [Bug 882]
Sun Nov 11 07:58:07 2001 Ossama Othman <ossama@uci.edu>
@@ -163,7 +164,7 @@ Sat Nov 10 19:27:36 2001 Ossama Othman <ossama@uci.edu>
- If some data was sent on a previous loop iteration then
return the number of bytes successfully sent.
- In both cases, errno is unchanged.
+ In both cases, errno is unchanged. [Bug 882]
Incidentally, this fixes a problem in TAO's SSLIOP pluggable
protocol when sending very large requests. Thanks to Andrew