[#XFIRE-309] Refactor Http transport to take advantage of persistent connections

XFire

Refactor Http transport to take advantage of persistent connections

Created: 16/Mar/06 09:13 AM Updated: 20/Mar/06 07:29 PM

Component/s:

Core

Affects Version/s:

1.0

Fix Version/s:

1.1-beta-1

Time Tracking:

Not Specified

Description

« Hide

Currently it appears a new HttpChannel is being created for each invocation, this in turn is creating a new HttpClient instance. If it were possible to refactor the Http transport stack to reuse HttpClient instances for a given uri then that would allow commons Http to automatically provide persistent connection support.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Dan Diephouse - 17/Mar/06 11:38 AM

I believe I've fixed this now in SVN. So it shoudl be in the upcoming beta release.

[ Permlink | « Hide ]

Mike Youngstrom - 17/Mar/06 11:50 AM

It turns out that our apps poor performance was due to a bug in the 1.5 VM. We upgraded to 1.5.0_06 and things went much faster. Regardless persistent connections is a nice to have anyway.

Thanks.

[ Permlink | « Hide ]

Dan Diephouse - 17/Mar/06 12:10 PM

realized that this isn't quite fixed yet anyway, I didn't update CommonsHttpMessageSender. doh!