On 14 Aug 2004 at 11:06, Gavin Lambert wrote: > > Trouble is I need it to work with a continuous stream of data, not > > discrete documents. So for example there may be multiple <head> blocks, > > or clashing element ids (say an <a name="foo"> at one point, then > > repeated exactly a bit further down). > > > > I need something which can deal with that sensibly and without errors -- > > ie, whenever it finds a clash, it just "forgets" about the earlier stuff > > and just uses the most recent one. Similarly, you almost never change > > pages, the data just keeps coming in until eventually it "falls off the > > top" of the scrollback history. In other words, you will *never* get an > > </html> (and only in exceptionally rare cases a </body>).
If you can send a "stream of div's" using xml-rpc polling, you can use the names (actually id's) to find previous elements with that id, delete them from the DOM, then use createElement and append them to the body. I can't see anyway of making this happen using the document's http transfer itself. That is, navigating to a URL and then expecting that same http stream to do this I think is not easily possible. But some javascript, a little xml-rpc and appropriate server and you can do what you want. -- Brad Clements, [EMAIL PROTECTED] (315)268-1000 http://www.murkworks.com (315)268-9812 Fax http://www.wecanstopspam.org/ AOL-IM: BKClements _______________________________________________ mozilla-embedding mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-embedding
