Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Message-ID: <828707681.1126603218950.JavaMail.jira@ajax.apache.org>
Date: Tue, 13 Sep 2005 11:20:18 +0200 (CEST)
From: "John Hawkins (JIRA)" <axis-c-dev@ws.apache.org>
To: axis-c-dev@ws.apache.org
Subject: [jira] Updated: (AXISCPP-748) Test: The TCP transmit message boundary
 is set by SO_SNDBUF.  What happens when the message > buffer?
In-Reply-To: <821138276.1121701634753.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/AXISCPP-748?page=all ]

John Hawkins updated AXISCPP-748:
---------------------------------

     Summary: Test: The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?  (was: The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?)
    Priority: Trivial  (was: Major)

Let's create a test for this and see what happens !

> Test: The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?
> -----------------------------------------------------------------------------------------------------
>
>          Key: AXISCPP-748
>          URL: http://issues.apache.org/jira/browse/AXISCPP-748
>      Project: Axis-C++
>         Type: Test
>   Components: Transport (axis3), Transport (Client)
>     Versions: current (nightly)
>  Environment: n/a
>     Reporter: Fred Preston
>     Priority: Trivial

>
> The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira