Lists Home |
Date Index |
- To: xml-dev <email@example.com>
- Subject: Re: [xml-dev] Breadth-First XML Serialization
- From: Marian Olteanu <firstname.lastname@example.org>
- Date: Wed, 8 Dec 2004 00:35:37 -0800 (PST)
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=BIPwR2SgIXHCyRqeWDHfSlQ5WoJ4WDQA69RoTv0FaiYK6aOd9TtqYkLx4KN40iKBdDCUK4uxQkuUl9xCoN6h+fDNHkvzFz+/HwiTQyrBZca/Ffgw8DMWjEZjtug21urKsL5cuRygTrDe+nr2DoTtDcSXkHI3UkmtSgrZ5RtXeh4= ;
- In-reply-to: <email@example.com>
So, what's the question?
First, breadth-first is not good for any application of the kind you menitioned. Optimal order of
data when an XML is transmitted over the network is application dependent.
Second, for the kind of application you mentioned later (a client that requests certain parts of
the document), I recomend technologies like Remote Scripting.
--- Simon Kissane <firstname.lastname@example.org> wrote:
> The standard text-based XML serialization is depth-first. So, for
> example, if the tree structure of my document is:
> |--- ElementA
> | |- ElementB1
> | | |- "Some text"
> | |- ElementB2
> |---- ElementC
> The standard depth-first XML serialization looks like:
> <ElementA><ElementB1>Some text</ElementB1><ElementB2/></ElementA>
> <ElementC><ElementD /></ElementC>
> But a breadth-first serialization could be something like:
> 1 0 Root
> 2 1 ElementA
> 3 1 ElementC
> 4 2 ElementB1
> 5 2 ElementB2
> 6 3 ElementD
> 7 4 "Some text"
> where the first number is the number of the DOM node in breadth-first
> document order, and the second number is the number of the parent DOM
> Such a serialization might be useful in some cases. Suppose for
> drill-down to show/hide sections and subsections of the document, and
> initially all the sections are hidden. Using the standard depth-first
> serialization, I have to wait until the whole document loads to see
> the entirety of the top-level, whereas with a breadth-first
> serialization I could see the top-level immediately.
> More generally, one could imagine a transfer mechanism for XML which
> enabled the application to prioritise part of the DOM tree. So, for
> example, I click the "expand" button the last section of my huge HTML
> document, while it is loading. The renderering engine now needs to
> know what is under that node urgently. So it could send a request to
> the server saying "send DOM nodes under this node urgently, then keep
> on sending me the rest." The server would interrupt its normal
> transfer order to send those DOM nodes straight away, and then would
> resume sending the document as usual.
> Simon Kissane
> Simon Kissane
> 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 subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.