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

Streaming XML? [was Re: XML Information Set Requirements..]

• From: Tim.Shaw@w...
• TO: cowan@l...
• Date: Mon, 22 Feb 1999 09:38:39 +0000

     This was one of my initial concerns on the DOM - I too will be working 
     on ticker-type streams.
     
     I nearly jumped in early in this conversation to agree with the 
     'others' - ie the SAX approach is just as important as DOM and the 2 
     should both be of similar (standards) status.
     
     I held off because I'm new to XML, and I wasn't sure if my alternative 
     wasn't too obvious to mention.
     
     I thought that each tick should be treated as a document. The client 
     would have to arrange that each 'document' so received would have to 
     be built, and then a document fragment extracted and inserted into a 
     client-held document (updating display etc. via DOM events as 
     appropriate).
     
     This approach requires the client of the XML data-source to be aware 
     of this of course, which may be a killer for genericity.
     
     Am I way off base here - and if so, could someone point me to current 
     thinking on this issue (I've browsed _a lot_ and seen little/nothing).
     
     Thanks
     
     tim


______________________________ Reply Separator _________________________________
Subject: Re: XML Information Set Requirements, W3C Note 18-February
Author:  cowan (cowan@l...) at unix,mime
Date:    19/02/99 22:06


Nathan Kurz wrote:
     
> And if the stream is continuous (for example, an XML
> stock ticker) even the concept of a well-formed stream seems tenuous.
     
It's not clear that XML supports infinitely long streams (where the 
end-tag of the document element is *never* reached).
     
-- 
John Cowan      http://www.ccil.org/~cowan              cowan@c...
        You tollerday donsk?  N.  You tolkatiff scowegian?  Nn. 
        You spigotty anglease?  Nnn.  You phonio saxo?  Nnnn.
                Clear all so!  'Tis a Jute.... (Finnegans Wake 16.5)
     
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... 
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981
-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message; 
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message; 
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • RE: Streaming XML? [was Re: XML Information Set Requirements..]
    • From: "Paul Butkiewicz" <arabbit@e...>
  • SAX and Standards Bodies (was Streaming XML?)
    • From: David Megginson <david@m...>

• References:
  • Re: XML Information Set Requirements, W3C Note 18-February-1999
    • From: John Cowan <cowan@l...>

• Prev by Date: Re: XML Information Set Requirements, W3C Note 18-February-1999
• Next by Date: Stateful http xml middleware w/ servlets?
• Previous by thread: RE: XML Information Set Requirements, W3C Note 18-February-1999
• Next by thread: SAX and Standards Bodies (was Streaming XML?)
• Index(es):
  • Date
  • Thread