Lists Home |
Date Index |
- From: "John Hicks" <firstname.lastname@example.org>
- To: "Tony McDonald" <email@example.com>, "xml-dev" <firstname.lastname@example.org>
- Date: Fri, 19 Mar 1999 10:37:08 -0800
How similar are the "140+ XML documents" you mention? How about put them in
a database and search there? Might be faster to search *before* you compose
final documents, not after; whether your database stores entire documents,
or just data for templates...
Cerium Component Software
Build Your Database Website with Our XML Team or Tools
XML Outline | XML DB | XML Servlet
212-662-3982 | 888-742-8989
"Software as a conversation with a community."
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of
> Tony McDonald
> Sent: Thursday, March 18, 1999 10:35 PM
> To: xml-dev
> Subject: Parsing XML->DOM and XSL querying optimising
> Hi all,
> I have an application that consists of 140+ XML documents, roughly 100k
> bytes each that I want to be able to query (using XSL pattern matching at
> present) and output to XML/HTML and RTF format. This will happen in real
> time (if at all possible).
> Additionally, I'd like to be able to search/query the entire repository of
> documents and return a composite XML/HTM or RTF document from these.
> At the moment, I'm experimenting with the DOM parser in Python and finding
> that a DOM parse takes about 4 seconds, whilst an XSL query takes
> about 1.8
> I reckon that a user could wait the 1.8 seconds for a query, but
> might start
> to get fidgety after almost 6 seconds (how transient we are!).
> What strategies have people got for limiting the DOM parsing time?
> My own thoughts are that I load up all 140 documents at
> server-startup time,
> parse them into DOM...DOM, store them into memory and then query
> each one in turn in the case of a simple query, and query all the DOM
> objects in the case of a full query across all XML documents.
> Is this sensible? practical? stupid?
> any thoughts on this would be appreciated,
> xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
> Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on
> CD-ROM/ISBN 981-02-3594-1
> To (un)subscribe, mailto:firstname.lastname@example.org the following message;
> (un)subscribe xml-dev
> To subscribe to the digests, mailto:email@example.com the
> following message;
> subscribe xml-dev-digest
> List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)