I will suggest you to use xml only for import/export and compatibility 
with the current implementation.
I have used succesfully SIXX for saving my data adn I like it a lot, but 
for a quite medium application with more then 100 users I will strong 
suggest to do not use XML as a storage medium.
XML is good for data manipulation but it is very very slow, and in my 
past project I passed a lot of time tring to optimize the XML 
transformer INSTEAD of testing or bug fixing.

Cees de Groot ha scritto  in data 02/01/2005 22.12:

> On Fri, 31 Dec 2004 16:15:55 -0500, Yanni Chiu <yanni at rogers.com> wrote:
>
>> I've got a look/work-alike of SqueakPeople, done with Seaside 2.3.
>> It's not feature complete (i.e. logged-in vs. not logged-in behaviour,
>> and the ranking computation). The data is saved in PostgreSQL.
>>
> Seaside is the least of my trouble (note that I think we want SqP to  
> publish static data "directly", e.g. with Kom or similar, so that we 
> have  clean static URL's just like SqP currently has). Biggest issue 
> for a  smooth transfer is the handling of SqP's XML data store, 
> especially w.r.t.  performance.
>
> What is the fastest XML parser for Squeak at the moment?



-- 
     Giovanni Giorgi           http://www.squeak.org
                               http://www.siforge.org
.............................................................