Menu
▾
▴
#97 Support for multi-threaded connection manager.
The Apache HTTP Client library includes a
multi-threaded connection manager. I've found it
necessary to use this connection manager when testing
our highly "AJAX-y" applications. Without it,
XmlHttpRequests that are long-lived will quickly
interface with normal user interface requests.
I downloaded the HTML unit source so that I could
modify and extend WebClient and HttpWebConnection to
support the creation and use of
MultiThreadedHttpConnectionManager as well as to
release those connections when the work has completed.
I'm sure you could easily integrate it so that is more
configurable and fits into the existing API.
Deryk
Logged In: YES
user_id=402164
Sounds interesting. Can you provide unit tests showing the
problem with the standard ConnectionManager and the benefit
of the multi threaded one?
Logged In: YES
user_id=1466555
Hi Marc,
Please investigate the reported bug:
https://sourceforge.net/tracker/?
func=detail&atid=448269&aid=1472606&group_id=47038
(Unit test is there) My hope is that this feature would
solve that problem as well.
Logged In: YES
user_id=1466555
Sorry, the right link to the bug is:
https://sourceforge.net/tracker/index.php?
func=detail&aid=1442428&group_id=47038&atid=448266
Logged In: YES
user_id=424834
The other bug that is mentioned does look a lot like what I
was experiencing. I imagine that adding a configurable way
to choose (per WebClient) which type of connection manager
to use would alleviate this issue.
I cannot easily provide a unit test from my code since it
would require our entire AJAX framework. However, the unit
test provided in the other bug looks like it would do the trick.
Logged In: YES
user_id=402164
MultiThreadedHttpConnectionManager is now the default.
Can you tell a bit (on the user mailing list) on your AJAX
experience with htmlunit? I guess that some additional
features would be helpfull (like turning async calls
synchronous) and that you're waiting for full support of
responseXML.