I never thought of that actually - interesting. So, I guess a GSOAP client wouldn't have a problem with the GSOAP Streaming, but another client (such as Axis) would?
Thanks again James Davanum Srinivas <[EMAIL PROTECTED]> 08/12/2005 18:02 Please respond to [email protected] To [email protected] cc Subject Re: Performance When Reading Attachments sounds like a GSOAP streaming problem. On 12/8/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Thanks Davanum. > > I wonder though, why I'm having my attachment problems. > [It's possible it's coded badly!] > Like, when I get my response from the GSOAP server, it's grand - but then > the attachment streams in after it (I watched it on TCPMon ) . > It's the waiting for the attachment that's causing my problem really - > that's where the delay lies. > > James > > > > > Davanum Srinivas <[EMAIL PROTECTED]> > 08/12/2005 16:11 > Please respond to > [email protected] > > > To > [email protected] > cc > > Subject > Re: Performance When Reading Attachments > > > > > > > not yet. > > On 12/8/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Thanks > > > > Would you recommend Axis 2 for better attachment performance? > > James > > > > > > > > > > Davanum Srinivas <[EMAIL PROTECTED]> > > 08/12/2005 12:39 > > Please respond to > > [email protected] > > > > > > To > > [email protected] > > cc > > > > Subject > > Re: Performance When Reading Attachments > > > > > > > > > > > > > > it is in 1.3 > > > > On 12/8/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > 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. > > > > > > > > > > > > -- > > 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. > > > > > > > -- > 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. > > -- 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.
