Lists Home |
Date Index |
- From: Paul Prescod <email@example.com>
- To: "'firstname.lastname@example.org'" <email@example.com>
- Date: Thu, 28 Jan 1999 13:27:36 -0600
"Matthew Sergeant (EML)" wrote:
> can use a persistent parsed structure like a DOM maintained in memory, but
> for some applications such as a rapidly changing XML database this isn't
> always feasible (or is it?).
You could continually update the DOMs based on changes in the XML. What
exactly are your concerns about this architecture.
> Currently our web based XML system processes
> about 5 files per second (very subjective figures) - and it's at max CPU
> (it's only a Pii266). This is using expat. Not a good situation since I
> could probably build a much faster application using an RDBMS - but I'm
> looking to the future when I can send the raw XML to the client.
You need to store data that is efficiently maintained relationally. You
need to *transmit* XML. Why not use a relational database and create XML
when you need it.
> Anyway, I'd like to hear people's comments on solving this potential issue,
> and whether they think choosing XML for the web was a good choice at this
> stage in browser development.
I don't follow the question. The longer we wait, the longer it takes
browsers to support it.
Paul Prescod - ISOGEN Consulting Engineer speaking for only himself
So what if one dark midnight less than a year from now, millions of
computers around the world suddenly grind to a halt? My computer grinds
to a halt several times a day. ... [Forget Y2K] We're ignoring a much
bigger bug problem that's hiding, well, right under our noses. Call it
the Y-Does-My-Computer-Crash-Three-Times-A-Day Problem.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)