Hi Checking the state saving algorithm I have seen that every time StateManager.saveView is called, it checks for duplicate ids, scanning the whole component tree. The documentation of StateManager.saveView says this:
"...This method must also enforce the rule that, for components with non-null ids, all components that are descendants of the same nearest NamingContainer must have unique identifiers....". Yes, that's right, but a possible optimization could be do not do it if project stage is production, or maybe just add a param that disable that stuff. Does that sounds good? Any objections? regards, Leonardo Uribe
