A channel backlog currently starts with a fixed number of messages and a link to the next page of older messages. We should add some minimal JavaScript to load this next page via AJAX and add these entries to the page without leaving the page.
This mechanism should be entirely transparent and load the exact same HTML page (no JSON, XML, whatever). This allows these pages to be cached easily (#5) without having to apply any custom processing logic otherwise. This means that the links can be loaded via AJAX or explicitly accessed through the link and both pages use the exact same URL and cache entry.
A channel backlog currently starts with a fixed number of messages and a link to the next page of older messages. We should add some minimal JavaScript to load this next page via AJAX and add these entries to the page without leaving the page.
This mechanism should be entirely transparent and load the exact same HTML page (no JSON, XML, whatever). This allows these pages to be cached easily (#5) without having to apply any custom processing logic otherwise. This means that the links can be loaded via AJAX or explicitly accessed through the link and both pages use the exact same URL and cache entry.