Using ozone as a persistent DOM

• To: ozone-users@ozone-db.org
• Subject: Using ozone as a persistent DOM
• From: Susannah Moat <S.Moat@cs.ucl.ac.uk>
• Date: Tue, 7 Aug 2001 15:02:35 +0100
• Delivered-To: lars@smb-tec.com
• Delivered-To: ozone-users-list@smb-tec.com
• Delivered-To: ozone-users@smb-tec.com
• Organization: University College London
• Reply-To: ozone-users@ozone-db.org
• Sender: owner-ozone-users@ozone-db.org

I was wondering if anyone could tell me if there was any way in which
you can optimise ozone for usage as a persistent DOM? We are wanting
to use ozone in our project to solve a memory problem we had with
large sets of XML documents, or simply one large document, not being
able to fit in memory. We do not need to worry about things like
problems being caused by concurrent access to the database, since this
will not occur, so I thought there may be a way to speed ozone up by
avoiding unnecessary operations required only for this sort of
purpose?

Thanks,

Susannah.

----------------------------------------------------------------------
Post a message:         mailto:ozone-users@ozone-db.org
Unsubscribe:            mailto:ozone-users-request@ozone-db.org?body=unsubscribe
Contact administrator:  mailto:ozone-users-owner@ozone-db.org
Read archived messages: http://www.ozone-db.org/
----------------------------------------------------------------------

• Prev by Date: Re: remoteID() use
• Next by Date: Large files
• Prev by thread: RE: [Dwengine-developers] Compile problem
• Next by thread: Large files
• Index(es):
  • Date
  • Thread