>>And if it has changed back to something you had two minutes ago, you'll still have to kill the current object and create the old one from scratch, and caching is your friend...
>>
>>Even more efficient would be to have a collection of such objects and keep only the relevant one visible. So instantiate on demand, add to collection. Next request, hide current object, check the collection, if found show it, if not add it.
>>
>>On destroy, just .remove(-1) on the collection, then remove the collection.
>
>The only problem with this approach is that you would need to use dynamic names for your container added to the page. If you would need to reference it outside this procedure, you may need to save the name of the currently active container in some property.

Perfect case for an _access method in its parent, isn't it?