No, the web service provider shouldn't need to do anything special in order for you to make an asynchronous web service call. Async[1] will help you if the call will take a long time to process (and the SOAP client can do something else while it's waiting), not necessarily in cases where you're just returning lots of data--the two cases are similar but not exactly the same.
If the data in the SOAP response can be more efficiently stored as binary instead of XML, MTOM[2] might be worth considering. Glen [1] http://www.jroller.com/gmazza/entry/creating_service_side_asynchronous_web (first paragraph for samples) [2] http://www.jroller.com/gmazza/entry/using_mtom_and_apache_fop Jessie914 wrote: > > Hello, > > I am a newbie to CXF. We have a web service server implemented by CXF V2.1 > (which cannot be changed), and now we are at the begining to develop the > web service client. The web service call will return large amount data. > > Will Aysnc calls help in this case? I am not sure if Aysnc mechanism > already implemented on the server side. (it is a prereq for client to > implement aysnc calls, isn't it?) > > Any best practise to improve the web service performance? > > Many thanks. > regards. > > -- View this message in context: http://old.nabble.com/Any-best-practise-to-make-CXF-better-support-large-amount-data-transmit-tp26569310p26569878.html Sent from the cxf-user mailing list archive at Nabble.com.
