12 Nov
2007
12 Nov
'07
1:35 p.m.
I beg to disagree. As PRImagePersistency is currently
implemented,
the only risk I can see is that it eventually fill up the disk, which
is actually a very minor trouble.
This is the standard implementation as I use it on all my web servers.
Propre persistency is something currently lackin in Pier, but the
issue will be tackled soon.
Instead, with the current setup, he would be always
starting from a
blank slate, want it or not, until he discovers he can save his work.
My fear is that most newbies won't discover http://localhost:8080/
seaside/tools/versionuploader before they give up.
The 'Seaside One-Click Experience' is not supposed to be a Magritte,
Pier, Scriptaculous, RSRSS, Comet, ... distribution, even though these
packages are all included. Its goal is to provide an easy start into
Seaside, for people that want to quickly take a look at it. I
originally created this package for a newbie tutorial I was giving at
the CHOOSE Forum 2007, Languages for the Web [1]. If people discover
Pier, that's fine, but this is not the goal.
Cheers,
Lukas
[1] http://www.choose.s-i.ch/Events/forum2007.html
--
Lukas Renggli
http://www.lukas-renggli.ch