Aerik Sylvan wrote:
I think the consensus is that once we have this, it will be very popular (from previous discussions on the mailing list). I asked Brion about this performance expectations once, and he said something like that he'd like to see it run in less than a second. I'm thinking that if it runs in 1 second +/- .5 secs, it might be okay, and having a ajax interface would make it palatable to the user experience (somehow waiting for a div to load seems less maddening than waiting for the whole page... plus, it might reduce some overhead associated with rendering the mediawiki page. OTOH... not friendly for mobile users etc... Hmm...)
Any AJAX interface would have to be optional.
Can we save the
results of a popular intersections (like American people intersected with Actors) so that the intersection is updated less frequently?
Yes, but then we have to add caching logic. You wouldn't want to save it too long, because then it becomes outdated.
Categories are obviously cached, so you just update the intersections when the categories get updated (or slightly less often).
(If I can find the time, I'll enhance the UI too.)
Don't worry about that yet. :)
Thanks again for the feedback,
Thank you for all your work.
Matthew Flaschen