Description
To increase performance of Activity Streams, we no longer do 3 searches to render the page:
- one for the stream
- then another 2 to see which of the next/previous arrows need displaying.
One solution is to instead provide a "More" button at the bottom of each activity stream, which will simply fetch the next 25 (50?) activity items from the server, and display them all on the same page.
Things to consider:
- we could still support the existing URL parameters to maintain compatability with any existing links
- we should audit all links in fisheye to ensure there are none already pointing to a streams search which has timestamp bounds
- e.g. the View in Activity Stream link on the changeset page, will need to still work - we will possibly need a similar "More" ajaxified link at the top of the stream too ?