5 Dec
2010
5 Dec
'10
11:55 a.m.
Lukas,
On 04.12.2010, at 21:49, Lukas Renggli wrote:
can you please elaborate a little on the specific actions that take place. I know
pier does a lot of traversal. But if I think about it I don't have a lot of ideas why
this is necessary.
Editing does not change the structure. It can create outgoing links that need to be looked
up. Moving to me includes managing of children if you move it to another hierarchy. But
the incoming links still just point to the same objects. I don't know what is needed
for copying. For removing neither it just produces broken incoming links. Did I miss a lot
of things I'm not aware of?
Would be kind to shed some light. Thanks!
Norbert
I had not
heard about any attempts to do this. Do you know why they
were not successful?
You wrote to me in Dezember 2009:
"I will obviously be interested in persisting my Pier sites in Magma.
I have examined the Pier model and grok'd the code related to
persistency, and from this have coded a new Persistency subclass,
PRMagmaPersistency (14 methods)."
I said: "Another thing I should warn you about is that Pier scans its
complete object graph whenever a page is edited, moved, copied,
removed, etc. The same happens when a live search is performed or when
a page is displayed with all its references enumerated. This basically
made my initial attempt of a persistency strategy using GOODS back in
2003 impossible. I don't know, but I guess this might be a problem for
Magma too, when the complete object graph is traversed several times
for every request?"