DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9931>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9931 Base64 decoder chokes on a whitespace: FASTER? ------- Additional Comments From [EMAIL PROTECTED] 2003-01-27 00:39 ------- I tested Martin's latest patch (Attachment 4553) and it passes the uncommented test. Also Martin and I discussed possibly adding a performance test with a much bigger piece of test data. If we decide to do this, we need to decide what constitutes "bad" performance. One idea that would not depend on the power of the machine on which the tests run is to time the encoding and decoding of a small piece of data (~ 1K to 5K) and then time the encoding and decoding of a larger piece (~100K to 500K) and make sure that the increase in running time is "acceptable". Currently, I imagine an O(n) algorithm would be acceptable so we could make the test guarantee a 100-110% increase in running time. We could do something similar for memory usage. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
