Lists Home |
Date Index |
- From: Pavel Velikhov <firstname.lastname@example.org>
- To: Paul Prescod <email@example.com>
- Date: Thu, 28 Jan 1999 16:06:16 -0800
Paul Prescod wrote:
> Pavel Velikhov wrote:
> > Paul Prescod wrote:
> > >
> > > 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.
> > Transmitting XML in a textual representation is not always a good idea.
> I don't follow you. XML is, by definition, textual.
I would like to view XML as a logical data model. I hope the actual
will be transparent in the future. I.e. the next generation xml "parser"
implements a DOM interface should be able to talk to an xml source that
is say an OODB and fetch small pieces of the document as they are
> > When the user does the 'select *' query on an XML database, sending him
> > a 20 megabyte XML file that he will need to parse, apply an xsl
> > stylesheet
> > to and display in the browser is not the best solution. IMHO, the result
> > of the query should be shipped on demand, when the user is actually
> > 'looking'
> > at a piece of an XML file.
> I don't think I said anything to contradict this, though I would say that
> by the time you have a "20 megabyte XML file" you've probably already done
> something wrong. There is almost never a good reason to generate files
> that large.
I agree, generating 20Mb XML files is bad. However it will happen. If
a lot of data available in XML by wrapping a relational database for
users/applications will be able to request large XML files.
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)