Wow, you measured the time required to SHA-1 and MD5 a URL and determined that calculation time is a bottleneck? Given modern CPU capabilities versus network and disk latencies, I would find that very surprising.<br><br><div>
<span class="gmail_quote">On 1/7/07, <b class="gmail_sendername">Renato Silveira</b> <<a href="mailto:renatosilveira@gmail.com">renatosilveira@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thank you all for the answers!<br>First of all I´ll try to increase the key size as Steve said. Because, the application that I´m working is perfomance oriented, so I think that we would have some problems with the overhead of Sha or MD5.
<br>I´m using java api of memcached as the client. The problem of whitespace in the url is solved because the client api use a URLEncoder in the key before the store the objects.<br>Well, as I´ll try this first approach and I tell you if it works!
<br></blockquote></div>