[jira] Created: (SOAP-166) streaming reponse payloads
Message: A new issue has been created in JIRA. - 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 1:50 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
[jira] Updated: (SOAP-166) streaming reponse payloads
The following issue has been updated: Updater: Bill Carpenter (mailto:[EMAIL PROTECTED]) 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
[jira] Commented: (SOAP-166) streaming reponse payloads
The following comment has been added to this issue: Author: Bill Carpenter Created: Wed, 7 Apr 2004 5:47 PM Body: Forgot to mention that the attached patch is against current CVS sources (as of 7 April 2004). - View this comment: http://issues.apache.org/jira/browse/SOAP-166?page=comments#action_28010 - 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:47 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
RE: eliminating one or two in memory copies of the response payload
wjc> I'm developing an obsession with getting rid of unnecessary wjc> copies during response processing. A patch for this is attached to bug SOAP-166: http://nagoya.apache.org/jira/browse/SOAP-166 I'd appreciate it if anyone who can would give it a try and report pro or con. For me, it gave 10-15% speed improvement and a pretty good memory footprint improvement. -- [EMAIL PROTECTED] (WJCarpenter)PGP 0x91865119 38 95 1B 69 C9 C6 3D 2573 46 32 04 69 D6 ED F3
Re: Apache license update
There is a new "nightly" release at http://cvs.apache.org/dist/soap/nightly/2004-04-07/. This has the new Apache license (finally), manifest files in soap.jar and soap.war (hurray), and a fix that trims the value in the HTTP Content-Length header. Scott Nichol Do not send e-mail directly to this e-mail address, because it is filtered to accept only mail from specific mail lists.
