[Owasp-esapi-c++] No Trie for now

[David Anderson]

I agree.

-David


On Aug 29, 2011, at 9:37 AM, "Kevin W. Wall" <kevin.w.wall at gmail.com> wrote:

> Also, I plan on bring this up at the ESAPI Summit at
> AppSec USA 2011. But I concur with this plan.
> -kevin
> 
> On Mon, Aug 29, 2011 at 9:31 AM, Daniel Amodio
> <dan.amodio at aspectsecurity.com> wrote:
>> We have been having an off list discussion about this, so I’m posting to the
>> list for public record.
>> 
>> 
>> 
>> Porting the Java version of Trie and HashTrie has been rather messy, and
>> requiring a lot of attention.
>> 
>> For the time being, we’re going to pull the Trie data structure and use
>> std::map instead.
>> 
>> 
>> 
>> There does not seem to be enough benefit to warrant the porting at the
>> moment. The Trie structure is only really being used for the HTML codec to
>> house the Unicode characters.
>> 
>> 
>> 
>> We will, arguably, loose minimal performance over this decision… and can
>> keep the Trie structure as a potential future enhancement. It makes more
>> sense to leave it out for now, and focus development time on more important
>> tasks.
>> 
>> _______________________________________________
>> Owasp-esapi-c++ mailing list
>> Owasp-esapi-c++ at lists.owasp.org
>> https://lists.owasp.org/mailman/listinfo/owasp-esapi-c++
>> 
>> 
> 
> 
> 
> -- 
> Blog: http://off-the-wall-security.blogspot.com/
> "The most likely way for the world to be destroyed, most experts agree,
> is by accident. That's where we come in; we're computer professionals.
> We *cause* accidents."        -- Nathaniel Borenstein
> _______________________________________________
> Owasp-esapi-c++ mailing list
> Owasp-esapi-c++ at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-esapi-c++