You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by ji...@apache.org on 2004/04/08 02:47:43 UTC
[jira] Updated: (SOAP-166) streaming reponse payloads

The following issue has been updated:

    Updater: Bill Carpenter (mailto:bill-apache@carpenter.org)
       Date: Wed, 7 Apr 2004 5:46 PM
    Comment:
The attached patch implements streaming responses for Call.invoke().  It doesn't do anything about streaming responses for Message.receive().
    Changes:
             Attachment changed to streaming-response-patch.txt
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/SOAP-166?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/SOAP-166

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: SOAP-166
    Summary: streaming reponse payloads
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Apache SOAP
 Components: 
             All
   Versions:
             2.3

   Assignee: 
   Reporter: Bill Carpenter

    Created: Wed, 7 Apr 2004 1:50 PM
    Updated: Wed, 7 Apr 2004 5:46 PM

Description:
Apache SOAP reads the entire response payload into memory and in most cases makes a few copies of it before returning results to the caller.  This is particularly troublesome in the RPC case (Call.invoke) because the String is fed into an XML parser which could just as well take in InputStream (or Reader).

Significant performance and memory footprint improvements can be had by streaming the response at least as far as the XML parser input.

PS:-  I am working on a patch for exactly this thing and will submit it soon.



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira