[ 
https://issues.apache.org/jira/browse/HTTPCORE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Kalnichevski resolved HTTPCORE-251.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.1.1

Patch checked in. Many thanks, Neeme.

Oleg

> fixes for src/docbkx/advanced.xml
> ---------------------------------
>
>                 Key: HTTPCORE-251
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-251
>             Project: HttpComponents HttpCore
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 4.1
>         Environment: 
> http://hc.apache.org/httpcomponents-core-ga/tutorial/html/advanced.html
>            Reporter: Neeme Praks
>            Priority: Minor
>             Fix For: 4.1.1
>
>         Attachments: advanced-diff.txt
>
>
> Section "3.1.1. HTTP line parsing and formatting", text "passed in memory" 
> should be "passed in-memory".
> Section "3.1.3. HTTP message parsers and formatter", text "provides a 
> coarse-grained facade type of interfaces" should be "provides coarse-grained 
> facade type interfaces". Or maybe even "facade-type"?
> Non-blocking HTTP request parsing / writing examples should use 
> non-deprecated API.
> BTW, there is an inconsistency between blocking and non-blocking API, in 
> non-blocking API, HttpRequestParser naming convention is deprecated in favour 
> of DefaultHttpRequestParser. However, this is not the case in blocking API.
> Blocking and non-blocking code examples in "3.2. Customizing HTTP 
> connections" should be swapped.

-- 
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]

Reply via email to