tag:blogger.com,1999:blog-5615146790866724994.post7645615004167553421..comments2009-02-15T04:38:43.945-08:00George S.http://www.blogger.com/profile/10755687529493368289noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5615146790866724994.post-73635117953459881612009-02-15T04:38:00.000-08:002009-02-15T04:38:00.000-08:00Thanks for your post.<BR/>I had similar problem and your solution is fantasticKarolhttp://www.blogger.com/profile/15549533506116902884noreply@blogger.comtag:blogger.com,1999:blog-5615146790866724994.post-85705278514932366662008-11-11T00:02:00.000-08:002008-11-11T00:02:00.000-08:00Thanks for this post.<BR/>I had a similar situation and after following your advice it works.<BR/>Cheers!Duckyhttp://www.blogger.com/profile/09265709849025236403noreply@blogger.comtag:blogger.com,1999:blog-5615146790866724994.post-47044175237341468442008-01-28T13:58:00.000-08:002008-01-28T13:58:00.000-08:00Have you tried to call more than 2 web services simultaneously. The problem that I have that there're several long (several minutes) web service calls that the app needs to make (potentially at the same time) while being able to process other (shorter) requests. I understand I cant have more than 2 HTTP connections to the same server but when I tried to share the same connection client calls would still be serialized (no more than 2 open connections). Any thoughts/ideas?jumbo_jet_zhttp://www.blogger.com/profile/10012497758760276899noreply@blogger.com