
Originally Posted by
crmalibu
You could store the urls in a cookie. But, there's limits to how much data can fit in a cookie, and in general, it's good to minimize the amount of data you put in a cookie.
An alternative would be to generate a unique id, and store this in a cookie. This id would be used to lookup the urls stored in a database which correspond to that specific id.
Both of these still have a limitation in that if the user clears/loses the cookie, thier list is essentially lost. If your users login with a username, then that would be a better way to maintain the association. It would also allow them to access the list from a different computer or browser, whereas the cookie solution would not.
Bookmarks