[ 
https://issues.apache.org/jira/browse/HTTPCORE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908528#comment-13908528
 ] 

Oleg Kalnichevski commented on HTTPCORE-375:
--------------------------------------------

I got almost lynched a few month back for suggesting that we start removing 
code in 4.x release series that has been deprecated for several consecutive 
feature releases. Do we or do we not want API compatibility between 4.x 
releases? Because if we do not, there are _way_ more important things that 
currently cannot be done due to strict API compatibility rules.

Oleg

> Remove unnecessary throws UnsupportedEncodingException
> ------------------------------------------------------
>
>                 Key: HTTPCORE-375
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-375
>             Project: HttpComponents HttpCore
>          Issue Type: Improvement
>          Components: HttpCore
>    Affects Versions: 4.4-alpha1
>            Reporter: Robin Skoglund
>            Priority: Minor
>             Fix For: Future
>
>         Attachments: HTTPCORE-375.patch
>
>
> StringEntity has constructors that unneccessarily declare 'throws 
> UnsupportedEncodingException'. This over-complicates client code because you 
> have to set up a lot of "this should never happen" exception handling.
> There's also a constructor that uses 'String.getBytes(String)', that should 
> instead be using 'String.getBytes(Charset)'.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to