[
https://issues.apache.org/jira/browse/HTTPCORE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525911
]
Roland Weber commented on HTTPCORE-110:
---------------------------------------
Hi Oleg,
thanks. I see your point with the init method, that was a mistake on my part. I
thought the parser and formatter would be created per message and pick up the
new line parser/formatter on that occasion. I'll drop the attributes along with
getters and setters from core. No need for extra factory methods, the
createRe*Parser and createRe*Writer methods are easy enough to override. They
are already consistent with NIO.
No need to revisit the header continuation discussion. It is just a minor issue
in my strive for perfection, and I wouldn't have time to work on it anyway.
cheers,
Roland
> refactor message parsing and formatting, step 2
> -----------------------------------------------
>
> Key: HTTPCORE-110
> URL: https://issues.apache.org/jira/browse/HTTPCORE-110
> Project: HttpComponents Core
> Issue Type: Improvement
> Components: HttpCore
> Affects Versions: 4.0-alpha5
> Reporter: Roland Weber
> Assignee: Roland Weber
> Fix For: 4.0-alpha6
>
> Attachments: 2k7-08-20-parser-1.txt, 2k7-08-23-parser-2.txt
>
>
> The line-level parsing and formatting for HTTP messages is spread across
> static helper methods in o.a.h.message. Refactor the code to allow for easy
> replacement of these parser and formatter elements, which are used by both
> core and NIO.
> Ideally, handling of header continuation lines, which is currently still
> implemented in specific parsers for blocking and NIO, could be factored out
> too. That would require a stateful parser.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
