Yes - I noticed this alright. So, will stream attachments stop the "blocking" nature of attachment reading?
Also, is this implemented in the Axis1.3 release, or will I have to go with the CVS version? Or is it Subversion now? Is there any guide as how to use the streaming method? Thanks for your help James Davanum Srinivas <[EMAIL PROTECTED]> 07/12/2005 18:17 Please respond to [email protected] To [email protected] cc Subject Re: Performance When Reading Attachments See http://issues.apache.org/jira/browse/AXIS-2221 there is support for streaming attachments. thanks, dims On 12/7/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi > > Can anyone help me with this at all? > > I'm considering using the current CVS build to see if any improvements > have been made. > > Like, I've heard about streaming attachments - they sound good - if I can > work out how to use them. > > But this is a critical area for my application, so if anyone has any > performance hints for DIME attachments at all I'd really appreciate it. > > > James > > > > > [EMAIL PROTECTED] > 06/12/2005 14:39 > Please respond to > [email protected] > > > To > [email protected] > cc > > Subject > Performance When Reading Attachments > > > > > > > Hi > > I'm really hoping someone can finally solve this for me. > > When I receive a message with a DIME Attachement, I get my Message object > back quite quickly, but it takes ages for it to read the attachments from > the message. > > I considered that this could be because it's waiting for the attachments, > but unfortunatly, I can't work out how to just read the attachments > straight away. > > Has anyone had this problem or found the solution? > > I am using Axis for my client, and someone else is using a C++ GSOAP > client, and they get the data in no time. > So any help in improving attachement performance would be appreciated . > > > Thanks > James > > > This email is intended solely for the use of the named addressee(s). Any > unauthorised disclosure, copying or distribution of the confidential > information contained therein, or the taking of any action based on it, is > prohibited. The sender disclaims any liability for the integrity of this > email. Legally binding declarations must be in written form. > > -- Davanum Srinivas : http://wso2.com/blogs/ This email is intended solely for the use of the named addressee(s). Any unauthorised disclosure, copying or distribution of the confidential information contained therein, or the taking of any action based on it, is prohibited. The sender disclaims any liability for the integrity of this email. Legally binding declarations must be in written form.
