[
Lists Home |
Date Index |
Thread Index
]
- From: "Paul Butkiewicz" <arabbit@earthlink.net>
- To: <Tim.Shaw@wdr.com>
- Date: Mon, 22 Feb 1999 19:39:26 -0500
Hi Tim. I did some work with this a few months ago and took the each tick
is a document approach. Unfortunately, I haven't really revisited it much
since. If you're interested, check out
http://home.earthlink.net/~arabbit/xmlnet I'm not trying to sell anything
(there was a commercial idea with some friends originally, but, eh. . .),
and you can have the source code if you want. Just curious, if you wanted
someone to bounce ideas off of, etc.
Paul Butkiewicz
arabbit@earthlink.net
-----Original Message-----
From: owner-xml-dev@ic.ac.uk [mailto:owner-xml-dev@ic.ac.uk]On Behalf Of
Tim.Shaw@wdr.com
Sent: Monday, February 22, 1999 4:39 AM
To: cowan@locke.ccil.org
Cc: xml-dev@ic.ac.uk
Subject: Streaming XML? [was Re: XML Information Set Requirements..]
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@locke.ccil.org) 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@ccil.org
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@ic.ac.uk
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@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following
message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
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@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following
message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
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@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|