You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Benjamin Sigg (JIRA)" <ji...@apache.org> on 2011/07/20 17:15:56 UTC

[jira] [Created] (HTTPASYNC-5) Allow customized LineParser / OperatedClientConnection

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-alpha1
            Reporter: Benjamin Sigg
            Priority: Minor


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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


[jira] [Updated] (HTTPASYNC-5) Allow customized LineParser / OperatedClientConnection

Posted by "Oleg Kalnichevski (Updated) (JIRA)" <ji...@apache.org>.
     [ 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:     (was: 4.0-alpha3)
                   4.0-beta1
    
> 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-beta1
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Updated] (HTTPASYNC-5) Allow customized LineParser / OperatedClientConnection

Posted by "Benjamin Sigg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HTTPASYNC-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Sigg updated HTTPASYNC-5:
----------------------------------

    Affects Version/s:     (was: 4.0-alpha1)
                       4.0-alpha2

> 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
>
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


[jira] [Updated] (HTTPASYNC-5) Allow customized LineParser / OperatedClientConnection

Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
     [ 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


[jira] [Resolved] (HTTPASYNC-5) Allow customized LineParser / OperatedClientConnection

Posted by "Oleg Kalnichevski (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HTTPASYNC-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski resolved HTTPASYNC-5.
---------------------------------------

    Resolution: Fixed

Benjamin,
I am sorry it took me so long to get around to fixing the issue. PoolingClientAsyncConnectionManager has been changed to provide a factory method to create a custom ClientAsyncConnection factory, which in its turn can create custom ClientAsyncConnection implementations.

Oleg
                
> 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-beta1
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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