Re: MD5Encoder.encode versus HexUtils.toHexString

2013-06-17 Thread Christopher Schultz
Chris, On 6/17/13 11:38 AM, Christopher Schultz wrote: >> Mark Thomas wrote >>> I haven't actually written any performance tests, but looking at the >>> code it seems that HexUtils.toHexString would execute slightly faster >>> for a 16-byte array because of repeated integer multiplication in the l

Re: MD5Encoder.encode versus HexUtils.toHexString

2013-06-17 Thread Christopher Schultz
Mark, On 6/16/13 12:04 PM, Mark Thomas wrote: > On 15/06/2013 16:39, Christopher Schultz wrote: >> All, >> >> While looking into a patch for BasicRealm, I noticed that there are two >> classes that convert byte[] to a hex-encoded string (e.g. byte[] { 1, 2, >> a, b ] -> "12ab"): HexUtils and MD5En

Re: MD5Encoder.encode versus HexUtils.toHexString

2013-06-16 Thread Mark Thomas
On 15/06/2013 16:39, Christopher Schultz wrote: > All, > > While looking into a patch for BasicRealm, I noticed that there are two > classes that convert byte[] to a hex-encoded string (e.g. byte[] { 1, 2, > a, b ] -> "12ab"): HexUtils and MD5Encoder. That isn't what those methods do. There are 2

MD5Encoder.encode versus HexUtils.toHexString

2013-06-15 Thread Christopher Schultz
All, While looking into a patch for BasicRealm, I noticed that there are two classes that convert byte[] to a hex-encoded string (e.g. byte[] { 1, 2, a, b ] -> "12ab"): HexUtils and MD5Encoder. MD5Encoder only has a single method (encode) and it does exactly what HexUtils.toHexString does, except