[
https://issues.apache.org/jira/browse/HTTPCORE-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548422#comment-13548422
]
Oleg Kalnichevski commented on HTTPCORE-325:
--------------------------------------------
Noah
(1) Fair enough
(2) There is nothing unfortunate about that. Heritrix has specific requirements
that are clearly out of scope as far as the HTTP protocol is concerned (message
archiving). It would be equally wrong to push Heritrix specific concerns down
to the underlying HTTP stack. If you are not comfortable just scanning for a
regex, you can always re-parse the message using HC parsing primitives (or your
own custom code). Saving a few lines of code on your end at th price of opening
up of HC internal code and tight coupling your code with it is just plain wrong.
Oleg
> support custom implementations of SessionInputBuffer and SessionOutputBuffer
> ----------------------------------------------------------------------------
>
> Key: HTTPCORE-325
> URL: https://issues.apache.org/jira/browse/HTTPCORE-325
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Affects Versions: 4.3-alpha2
> Reporter: Noah Levitt
> Attachments: httpcore-325-20121231182846.diff
>
>
> In heritrix we have a set of classes that wrap streams and record them
> verbatim for replay. One of the things it needs to do is make a note of where
> the http headers end and the message body begins. In order to make this work
> with httpcomponents I found I needed custom implementations of
> Session*Buffer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
