18 Dec
2009
18 Dec
'09
3:44 p.m.
Having the instance cached during the session sounds
like the behaviour
I'd have expected to get by default, so it's good to know that is indeed
how things are supposed to be.
That's a very strange bug, because I have sites that depend on the
correct behavior. It must have been introduced recently, but I have no
idea where?
To avoid misunderstanding for anyone reading, I'll
point out that this
potential bug is not the total answer to my original post. Essentially,
how do I get my component instances (or at least certain parts of their
state) to persist *beyond* the session, in much the same way as a newly
created page will persist?
Components are view and controller. If you have data that should
persist across sessions, you should put it into a separate model
object. Pier stores its model in the PRKernel instance, that refers to
a tree of PRStructure objects, and others.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch