You are viewing a plain text version of this content. The canonical link for it is here.

Posted to xmlrpc-dev@ws.apache.org by bu...@apache.org on 2003/05/18 18:43:37 UTC

DO NOT REPLY [Bug 20022] New: - Use a larger size for the BufferedOutputStream

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20022>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20022

Use a larger size for the BufferedOutputStream

           Summary: Use a larger size for the BufferedOutputStream
           Product: XML-RPC
           Version: 2.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Source
        AssignedTo: rpc-dev@xml.apache.org
        ReportedBy: theis.news@gmx.at


In LiteXmlRpcTransport, the BufferedOutputStream is created with the default
buffer size of 512 bytes. This is pretty small, even smaller than the MTU, and
might cause the request to be sent in 2 calls. After each call the socket will
wait for the (TCP stack) ACK from the server, but the TCP stack there will delay
sending the ACK until more packets are to be acknowleged (that will not happen)
or a timeout. A default size of about 1500 (the max. possible MTU) or even
larger (and let the TCP stack devide the request into packets) would be nice. Or
even better a configurable buffer size :)