From: RBRi <rb...@us...> - 2020-03-08 18:12:08
|
There was a lot refactoring done in the past. Have done a check and think your point was already solved. Additionally i have removed the method getHostConfiguration completly because. --- ** [feature-requests:#146] Do not recreate host configuration per-request** **Status:** open **Group:** **Labels:** Interface Improvements (example) **Created:** Fri Jul 03, 2009 11:12 PM UTC by Daniel Radetsky **Last Updated:** Sun Oct 21, 2012 04:15 AM UTC **Owner:** nobody Currently, getResponse calls getHostConfiguration, which creates a new HostConfiguration and then modifies it based on the WebRequestSettings. Instead, the WebClient should have a member HostConfiguration, which it modifies based on the request settings. Optionally, the member configuration could be copied for getResponse and then modified for the request based on the request settings. This might be better, since: 1. Different concurrent requests could have different configurations. 2. If some part of the codebase expects that each request has its own HostConfiguration (are they modified, perhaps?), this expectation would not be disappointed. --- Sent from sourceforge.net because htm...@li... is subscribed to https://sourceforge.net/p/htmlunit/feature-requests/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/htmlunit/admin/feature-requests/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |