Multiple component state preservation???
Posted: Wed Jul 04, 2007 12:08 pm
Typically a web page/web site will only have a single component/system which persists state across requests, such as the pagination of a list of users.
I am at the point in my framework where I have to make the choice, do I build in native support for multiple components to persist state on a single page at a time or not.
Obviously it would be neat although I not sure entirely practical and the over head in code complexity goes against Agile for sure.
Can you think of a rock solid reason why I may want two or more components to persist state across multiple requests?
For instance, consider the possibility of having a search engine listings like Google, where I have two distinct but related listings:
a. Standard
b. Premium
It might be neat for the Standard listings to retain it s pagination state & keywords while allowing the user to page through the premium listings as well, without changing or clearing the state of the standard listings.
The implementation is complicated but for good reason, it essentially hides all those details from the component developer, basically there is no need for the component developer to have knowledge of that fact that it needs to retain state, etc, this is all handled by the framework.
So I ask, can you think of any scenarios where this would be a useful or desire functionality? Please provide examples so I can take them into consideration before begining implementation or skipping onto the next requirement.
Cheers
I am at the point in my framework where I have to make the choice, do I build in native support for multiple components to persist state on a single page at a time or not.
Obviously it would be neat although I not sure entirely practical and the over head in code complexity goes against Agile for sure.
Can you think of a rock solid reason why I may want two or more components to persist state across multiple requests?
For instance, consider the possibility of having a search engine listings like Google, where I have two distinct but related listings:
a. Standard
b. Premium
It might be neat for the Standard listings to retain it s pagination state & keywords while allowing the user to page through the premium listings as well, without changing or clearing the state of the standard listings.
The implementation is complicated but for good reason, it essentially hides all those details from the component developer, basically there is no need for the component developer to have knowledge of that fact that it needs to retain state, etc, this is all handled by the framework.
So I ask, can you think of any scenarios where this would be a useful or desire functionality? Please provide examples so I can take them into consideration before begining implementation or skipping onto the next requirement.
Cheers