Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Message-ID: <20515420.1198332943012.JavaMail.jira@brutus>
Date: Sat, 22 Dec 2007 06:15:43 -0800 (PST)
From: "Oleg Kalnichevski (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Subject: [jira] Commented: (HTTPCLIENT-716) application-defined routes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HTTPCLIENT-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554120 ] 

Oleg Kalnichevski commented on HTTPCLIENT-716:
----------------------------------------------

Roland

My only concern is that this all involves too many map lookups. I know it is too early to start thinking about performance optimizations, but nonetheless performance is an important factor we ought not neglect. Could we eliminate context lookup? This will also make the logic somewhat simpler.

Oleg  

> application-defined routes
> --------------------------
>
>                 Key: HTTPCLIENT-716
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-716
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpClient, HttpConn
>    Affects Versions: 4.0 Alpha 3
>            Reporter: Roland Weber
>            Priority: Minor
>             Fix For: 4.0 Alpha 3
>
>
> Allow applications to specifiy a route as request parameter (or in the context).
> This functionality is a replacement for RoutedRequest, which is removed by HTTPCLIENT-715.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org