We do need to test HTTPS, so I tried the new HTTP Request HTTPClient (Alpha). It doesn't show this behaviour. I'm using the number of used local ports as a measure, something like netstat|grep https|wc -l to watch it. It's promising, the number of connections permanently corresponds the number of threads. Some results I got, using a thread group, 10 threads, iterating one minute:
HTTP Request: between 9 and 10 connections, 1260 requests. HTTP Request with keep-alive: growing to 389 connections, 1027 requests. HTTP Request HTTPClient (Alpha): between 9 and 10 connections, 1225 requests. HTTP Request HTTPClient (Alpha) with keep-alive: 10 connections, 1267 requests.
What restrictions do I have to expect, when using the HTTP Request HTTPClient-Alpha? Did anybody recognize bugs? Or is it allready used a lot?
Thanks.
Felix van Hove
-- easynet GmbH (http://www.de.easynet.net) Felix van Hove, system integration Harburger Schlossstrasse 1, D-21079 Hamburg fon: +49-40-77175-457, fax: +49-40-77175-498 # easynet is part of the easynet group plc (www.easynetgroup.net)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
