Michael Rogers wrote: > Edgar Friendly wrote: >> These lists might grow large, so some way of shortening may be useful >> (only recently changed ratings, only posting BAD ratings n times/days). > > Instead of incorporating the list itself, every post could contain a key > pointing to the user's ratings - only the users who marked that user > GOOD would need to retrieve it, and only once per day or so.
It's more complex, but maybe only use redirects for large rating lists. I like the simplicity of including a few recent changes of rating to posts. Referring to a rating list brings the problems of managing this ratings list. If we don't have per-identity boardlists (and thus one reference list per board), we'd need # users * # boards keys to request to check for updated ratings, and there'd be huge overlap between these (as much overlap as users who post on multiple boards). And if we do have per-identity boardlists, we can have one rating key per identity, but have to deal with updating that key, re-inserting it with new ratings, blah blah. If we can include ratings in a users' post then this extra hassle can be minimized. Maybe both - as many ratings as we can fit in a single key with a redirect to the current master-list of ratings for that user. E. _______________________________________________ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
