[
https://issues.apache.org/jira/browse/HTTPASYNC-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPASYNC-5:
--------------------------------------
Fix Version/s: 4.0-alpha3
> Allow customized LineParser / OperatedClientConnection
> ------------------------------------------------------
>
> Key: HTTPASYNC-5
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-5
> Project: HttpComponents HttpAsyncClient
> Issue Type: Wish
> Affects Versions: 4.0-alpha2
> Reporter: Benjamin Sigg
> Priority: Minor
> Fix For: 4.0-alpha3
>
>
> The "org.apache.http.message.LineParser" interface is responsible for reading
> the HTTP response header. In the current version of the async-http-client
> there is no way to replace the default BasicLineParser with a custom
> implementation. A custom implementation would be required to support
> additional formats that are similar yet not exactly the same as HTTP (e.g.
> ICY).
> At the moment the documentation tells us to override
> "DefaultNHttpClientConnection.createResponseParser" to introduce a new
> LineParser. But it is not possible to smuggle a subclass into to the http
> client because "ClientConnAdaptor.open", which uses this
> "OperatedClientConnection", just creates a new "DefaultNHttpClientConnection"
> object.
> An easy solution might be to allow clients to set a default LineParser. On
> the other hand allowing clients to choose the "OperatedClientConnection"
> might be a better long term solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
