Okay, here's how it worked:<br><br>All URLs in a JavaScript array. One cookie for each URL (cookie name *is* the URL, to make it simple).<br>When the page loads, it reads the cookies and orders the URLs by the numeric value (highest to lowest).
<br><br>The page loads the links in three columns, so the top left is the most-used, top middle is the second-most used, and so on.<br><br>Every time an onclick is fired for a link, it increments the cookie value by one. So links aren't re-sorted by popularity until a page is refreshed.
<br><br>To prevent formerly-popular but now unused links from reigning supreme, I had some sort of logic by which once any link reached a number greater than x (I forget), every single cookie's value is multiplied by itself times
0.75 or something like that.<br><br>If I find the code I'll post it. It was at least three years ago when I did this.<br><br>Shawn<br><br><div><span class="gmail_quote">On 2/17/06, <b class="gmail_sendername">Paul Novitski
</b> <<a href="mailto:paul@novitskisoftware.com">paul@novitskisoftware.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;">
At 08:53 AM 2/17/2006, Shawn Milo wrote:<br>>I want a page of my personal bookmarks which automatically sorts by<br>>frequency of use.<br><br>Sounds like a nice utility; I'm interested. How did you persistently<br>
store total page-requests using JavaScript? Like you, I think I'd<br>rather do this server-side, but the client-side problem is intriguing.<br><br>Paul<br><br>_______________________________________________<br>Javascript mailing list
<br><a href="mailto:Javascript@LaTech.edu">Javascript@LaTech.edu</a><br><a href="https://lists.LaTech.edu/mailman/listinfo/javascript">https://lists.LaTech.edu/mailman/listinfo/javascript</a><br></blockquote></div><br>