[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re:Re: Re: requesting XML document retrieved from a large and complexone

• From: "Ju, Hong-Taek" <juht@p...>
• To: "Thomas B. Passin" <tpassin@h...>, xml-dev@l...
• Date: Wed, 08 Aug 2001 15:11:14 +0900

Thanks for your valuable comments.

As you recommended, DOM tree in memory and XSLT might be best option.
But I worry about memory lack for a large and complex document,
Can I ask one more favor of you?
How can I keep a DOM tree in memory by way of high memory efficiency?
Does the problem depend on implementation?

Thanks again

/juht

>-----Original Message-----
>From: Thomas B. Passin [mailto:tpassin@h...]
>Sent: Wednesday, August 08, 2001 9:42 AM
>To: xml-dev@l...
>Subject: Re: Re: requesting XML document retrieved from a large
>and complex one..
>
>
>[Ju, Hong-Taek]
>
>> The use of SAX filter in server is also inefficient in terms of server.
>> Because the server must generate large source document, even if filterd
>> after all.
>
>Not necessarily.  Of course, it depends on your source documents and your
>needs.  The SAX filter does have to parse the entire document, but that in
>itself is not terribly demanding on resources.  Your SAX filter does not
>need to save anything except the parts that you want.
>
>> If a server have a ability to generate a necessary part of
>source document
>> on the ground of a client request.
>> The sever can save a computing resources.
>> On the assumption a client specify a part of source document in XPath
>> string.
>
>All xpath engines, I believe, must build a DOM in memory before being able
>to apply a path expression.  This would be a much bigger
>processing load and
>much slower.
>
>> Is it passible for server to generate a requested part of source document
>on
>> the ground of  XML shema (DTD or Schema) of source document?
>>
>
>You'd have to use a system that could index the source document if you want
>to avoid analyzing for each request.  So maybe you want to use some kind of
>an object-oriented or xml database, one that can use indexes.
>
>If all the requests were for parts of the same document, you cou;d create a
>DOM, keep it in memory, and give it to an xslt processor each time you need
>to service a request.
>
>Cheers,
>
>Tom P
>
>
>
>------------------------------------------------------------------
>The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>initiative of OASIS <http://www.oasis-open.org>
>
>The list archives
>are at http://lists.xml.org/archives/xml-dev/
>
>To unsubscribe from this elist send a message with the single word
>"unsubscribe" in the body to: xml-dev-request@l...
>

• Follow-Ups:
  • Re: Re:Re: Re: requesting XML document retrieved from a large andcomplex one..
    • From: "Thomas B. Passin" <tpassin@h...>

• References:
  • Re: Re: requesting XML document retrieved from a large and complexone..
    • From: "Thomas B. Passin" <tpassin@h...>

• Prev by Date: Another "Against the Grain" column on XML
• Next by Date: RE: Another "Against the Grain" column on XML
• Previous by thread: Re: Re: requesting XML document retrieved from a large and complexone..
• Next by thread: Re: Re:Re: Re: requesting XML document retrieved from a large andcomplex one..
• Index(es):
  • Date
  • Thread