Ralph Johnson <johnson(a)cs.uiuc.edu> wrote:
External SIXX persistance exists.
I haven't looked at it yet, but I am skeptical. Do you think
it will do what I want? XML is just barely human readable.
It tends to be slow. It is OK for a least common denominator,
but you can almost always do better.
I've experimented a bit with SIXX persistence. I had intended
to use it to move the contents of a SmallWiki server running on
VW to Squeak.
There were two problems:
a. The root SmallWiki folder has the Swazoo server
as a dependent. Consequently, SIXX tries to persist
the Swazoo server, and generates noncompliant
XML that cannot be parsed. To avoid this, break
the dependency before persisting, then restore it.
b. The Squeak version is older than the VW, and is
missing some classes/inst vars. I didn't explore porting
the most current version.
As to SIXX as a persistence strategy:
Seems to me that SIXX's intended as a maximally
portable mechanism for moving data cross-dialect.
Readability and performance are not a concern --
the SIXX format is massive, slow and not
suitable for modification.
I'd aim at database storage for SmallWiki.
Postgresql and SQLite seem like good choices.