See D18006 for discussion, this view library potentially makes a lot of DB calls with the markup engine, it should be batched (since I'm probably going to drop in replace the History view in Diffusion with it.
|Resolved||chad||T12824 Redesign Diffusion|
|Wontfix||epriestley||T12749 Performance test and tune DiffusionHistoryListView|
I think using a Pool (like HandlePool) is not too much more work (at least, if I'm implementing it) than AJAX it and will be useful in more cases. I believe we need the Pool implementation regardless, sooner or later.
If you're comfortable doing an AJAX implementation and want to hook that up, I think that's fine to ship and then I can replace it with a Pool implementation when I have a chance. If this is ending up on my plate either way, I don't think there's a big time savings from doing AJAX.
(There's also maybe some interaction with T9713 here, although we could retrofit that easily enough later.)