Scott Mitchell 27a2017f7f Opportunity for lazy initialization in Headers interface ... Motivation: The Headers interface had two member variables (addAllVisitor, setAllVisitor) which are not necessarily always needed but are always instantiated. This may result in excess memory being used. Modifications: - addAllVisitor will be accessed via a method addAllVisitor() which will use lazy initialization. - setAllVisitor will be accessed via a method addAllVisitor() which will use lazy initialization. Result: Potential memory savings by using lazy initialization.		2015-01-21 13:48:52 -05:00
..
main/java/io/netty/handler/codec	Opportunity for lazy initialization in Headers interface	2015-01-21 13:48:52 -05:00
test	Motivation: Sonar points out an equals comparison, where the types compared are different and don't share any common parent http://clinker.netty.io/sonar/drilldown/issues/io.netty:netty-parent:master?severity=CRITICAL#	2014-12-16 07:17:31 +01:00