[ http://issues.apache.org/jira/browse/HTTPCORE-5?page=comments#action_12418845 ]
Oleg Kalnichevski commented on HTTPCORE-5: ------------------------------------------ Changelog: ------- * Header, HeaderElement, NameValuePair, RequestLine and StatusLine changed to interfaces. The default implementation of these interfaces moved to o.a.http.message package. * The org.apache.http API no longer contains any parsing and formatting code and does not imply any specific physical representation of HTTP messages and their elements * HTTP messages and their elements can be lazy-parsed / processed on demand potentially improving performance and reducing memory footprint * HTTP elements can be backed by different low-level data primitives. For instance this enables the use of java.nio buffers as physical data containers for HTTP elements, which _may_ be required for HttpNIO. Please review and let me know what you think Oleg > Make Header an interface > ------------------------ > > Key: HTTPCORE-5 > URL: http://issues.apache.org/jira/browse/HTTPCORE-5 > Project: HttpComponents Core > Type: Improvement > Components: HttpCore > Versions: 4.0-alpha2 > Reporter: Oleg Kalnichevski > Assignee: Oleg Kalnichevski > Fix For: 4.0-alpha3 > > Folks, > Would anyone strongly object the change to make Header an interface? I am > presently looking into further optimization of the HttpCore header processing > code and see a potential benefit from having different Header implementations > (for instance, one backed by a char array lazy parsed on demand) I also think > HttpNIO might need a different Header implementation. > Oleg -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - 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]
