With functionality growth more and more contexts output a huge text... Some clients may handle such huge messages slowly. Anyway such messages are not readable and sometimes users do not want to receive such huge messages (e.g. user requested for issues list but did not know that there is a huge number).
Making pagination for each context is not accessible, I believe... So the idea is to create Pagination context. Which would “catch” huge messages in output filter and split them into smaller. This context would store split messages in internal buffer and will output the them on requests. Samples:
User: Show page 2 User: Next page User: Next
#1 Updated by Andriy Lesyuk about 12 years ago
- Tracker changed from Feature to Enhancement