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><br>tks again!<br><br>Renato<br><br><br><br><br><br><br><div><span class="gmail_quote">On 1/5/07, <b class="gmail_sendername">Marc</b> <<a href="mailto:Marc@facebook.com">Marc@facebook.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;">
<div>
<font face="Verdana, Helvetica, Arial"><span style="font-size: 12px;">I misspoke about whitespace...the server will drop it, not the client.<div><span class="e" id="q_10ff3bf0a632cf2d_1"><br>
<br>
<br>
On 1/5/07 11:25 AM, "Marc" <<a href="mailto:Marc@facebook.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Marc@facebook.com</a>> wrote:<br>
<br>
</span></div></span></font><div><span class="e" id="q_10ff3bf0a632cf2d_3"><blockquote><font face="Verdana, Helvetica, Arial"><span style="font-size: 12px;">I see two possible problems. First – as you note – the client needs to deal with the increase too. I'm not sure which one you're using but for most implementations, the default read -buf size for GET results is 250+1 so, if memcached is returning results like:
<br>
VALUE very<250>long_key 0 3\r\nxxx\r\nEND <br>
It very well may be the case that the client punts after scanning "VALUE very<250>" without seeing either space (\b) or CRLF (\r\n)<br>
<br>
Second, if you have spaces in your URL this will cause similar problems. The client will take the following:<br>
VALUE <a href="http://url/key/with" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://url/key/with</a> white space 0 3\r\nxxx\r\nEND<br>
<br>
as the value for key "<a href="http://url/key/with%C2%B2" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://url/key/with"</a> and not finding a corresponding client request for that key will most likely discard it.
<br>
<br>
On 1/5/07 11:08 AM, "Renato Silveira" <<a href="mailto:renatosilveira@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">renatosilveira@gmail.com</a>> wrote:<br>
<br>
</span></font><blockquote><font face="Verdana, Helvetica, Arial"><span style="font-size: 12px;">Hi,<br>
<br>
I´m using memcached as a URL keyword cache. The url is the key and the cached object is a string with relevant keywords of the site. Well, it´s working fine for my purpose. The only problem is the limit of key size to 250 bytes(because there can be url bigger than 250 bytes). Well, I tried to increase the value of the constant KEY_MAX_LENGTH to 2048 bytes. I recompile memcached and it´s not working. Should I have to make any modification on the client API? Does anyone can helpme with this issue?
<br>
<br>
tks!<br>
<br>
Renato<br>
<br>
</span></font></blockquote><font face="Verdana, Helvetica, Arial"><span style="font-size: 12px;"><br>
<br>
</span></font></blockquote><font face="Verdana, Helvetica, Arial"><span style="font-size: 12px;"><br>
</span></font>
</span></div></div>
</blockquote></div><br>