This is a little survey to collect some valid use-cases for stateful web components. Note that I'm not talking about conversational state nor stateful session beans. I'm solely interested in web components that handle their own state (as in JSF) and what you use them for.
I don't understand - what good is a web component that /doesn't/ have state? What would you transfer to the browser/UA?
posted by Anonymous on Mar 6, 2006 7:32 PM
Re: Valid use-cases for stateful web components?
Well I am maybe missing something. The web components I've seen floating around, button, label, list, ... are widgets that render according to an underlying model. They trigger events and present data. I think I'm missing something though, that's why I ask the question.
posted by Geert Bevin on Mar 6, 2006 7:37 PM
Re: Valid use-cases for stateful web components?
Hm, tables remembering current pages and sort-columns, trees remembering their state, tab-panels remembering, which one's seleted. Almost any non-trivial component, it seems ...
