1 Aug
2006
1 Aug
'06
9:39 p.m.
Dear Damien,
I am also working on the persistency issue, I need something working
well as soon as possible. Content authors for my site are nagging me
already, we go live in October.
I figured that magma was at least worth a try. As as DB it is all
in the
smalltalk image without any dependency upon external servers. Magma
appears to be aiming to make persistency as simple as possible. Raw
performance is unlikely to be an issue for me. It seems like the
right fit.
I would have had something working by now if it were not for my
windows
installation taking a dive due to disk errors. I am now up and running
again (just about). In the next couple of days/weeks I should have
something to show for my troubles.
If you want to try magma with seaside there are some updates/bug fixes
around (email me or, check recent history of the magma list
because the
repository has yet to be updated)
Hi Keith
I would really be interested to learn more about it.
I thought that using a changeset-like mechanism for a domain that is
open (and can be extended)
is a problem and may break the restoring facilities.
I was thinking that we could at least save the page in XML or a
similar format after each command.
and we could recover the lastest changes.
Will you publish and share your code?
I would love to get a Smallwiki version whose image could get
corrupted and that I could reconstruct :)
Stef