Lists Home |
Date Index |
- From: "Matthew Sergeant (EML)" <Matthew.Sergeant@eml.ericsson.se>
- To: "'James Robertson'" <firstname.lastname@example.org>, email@example.com
- Date: Tue, 2 Feb 1999 10:11:09 +0100
> -----Original Message-----
> From: James Robertson [SMTP:firstname.lastname@example.org]
> At 20:29 1/02/1999 , Matthew Sergeant (EML) wrote:
> | My problem was slightly different. I needed to be ready for the 5.0
> | (probably IE5, although I'd prefer NS5), and XML seemed ideal because
> | would be displaying/editing documents that look like data (or data
> | looks like a document if you like). We really needed an object
> database, but
> | I needed to get moving quickly (a typical web project: "Can we have it
> | yesterday"). Learning an object database wasn't a possibility. I
> | knew XML. So I looked at it like this - we could have it 2 ways:
> | 1) Store XML now, process into HTML now, Transmit XML in the future.
> | 2) Store in RDBMS now, process into HTML now, process into XML in the
> | future.
> I would personally recommend a third option:
> 3) Store in RDBMS now, process into XML, process this into HTML now.
> Process the XML into whatever you want in the future.
This generates probably 5% more overhead than I have already (the
RDBMS). XML doesn't parse quickly (well, OK, it parses quickly, but not
compared to reading data from an RDBMS). When you are processing tens of XML
files per second this becomes a huge problem.
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/
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)