Meta tags:
description=We all know how to make an AJAX request, and fetch some data. But as soon as you need to fetch data incrementally, have the server push data to you, you...;

Headings (most frequently used words):

by, emil, stenström, partial, xmlhttprequest, responses, comments, mark,

Text of the page (most frequently used words):
the (19), data (10), you (9), that (8), with (8), #xmlhttprequest (7), this (7), way (6), xhr (6), var (6), twitter (5), but (5), 2012 (4), streaming (4), get (4), and (4), new (4), all (4), parse (4), curr_index (4), last_index (4), partial (4), one (3), emil (3), stenström (3), your (3), against (3), have (3), web (3), see (3), cross (3), would (3), like (3), know (3), method (3), responsetext (3), url (3), responses (3), mark (2), need (2), from (2), may (2), javascript (2), api (2), origin (2), not (2), problem (2), mixed (2), mime (2), jan (2), really (2), curl (2), there (2), easy (2), implement (2), can (2), some (2), make (2), ideally (2), use (2), without (2), stuff (2), server (2), side (2), callback (2), client (2), will (2), only (2), after (2), open (2), abort (2), interval (2), function (2), seconds (2), for (2), content (2), chunk (2), domain (2), think (2), fetch (2), different (2), friendly (2), bit (2), jump (2), yeah, modified, used, titanium, tried, got, error, allowed, access, control, allow, found, around, interesting, idea, multipart, replace, type, http, wikipedia, org, wiki, replace_, 28experimental, comments, far, behind, https, stream, com, statuses, filter, json, track, keyword, nick, working, annoying, something, liner, 100s, lines, code, technologies, browser, platform, possible, set, headers, existing, apis, adding, custom, just, each, time, sends, specified, parameter, native, numerous, hacks, are, out, fills, these, requirements, please, let, love, better, biggest, property, keeps, filling, longer, receive, bigger, memory, fixed, today, simply, kill, connection, certain, amount, has, been, received, again, 25000, clearinterval, settimeout, 5000, setinterval, check, every, log, console, substring, return, length, define, response, send, true, own, cors, note, tested, webkit, allows, requests, works, firefox, too, definitely, work, sorry, simplest, almost, workds, first, read, about, them, should, more, recognition, progressive, xmlhttprequests, kyle, schulz, blog, how, ajax, request, soon, incrementally, push, resort, sorts, complicated, websockets, their, versions, shady, support, kinds, polling, hidden, iframes, activex, modern, feed, contact, navigation,

Text of the page (random words):
partial xmlhttprequest responses friendly bit jump to content or jump to navigation friendly bit contact feed partial xmlhttprequest responses jan 8 2012 emil stenström js modern web we all know how to make an ajax request and fetch some data but as soon as you need to fetch data incrementally have the server push data to you you have to resort to all sorts of complicated stuff websockets with all their different versions and shady support different kinds of polling hidden iframes activex for ie the simplest way that almost workds is partial xmlhttprequest responses i first read about them as progressive xmlhttprequests on kyle schulz blog but really think that method should get more recognition note i ve only tested this with webkit against twitter s streaming api with a xmlhttprequest that allows cross domain requests i think it works with firefox too but it will definitely not work in ie sorry var xhr new xmlhttprequest var url streaming url on you own domain or cors xhr open get url true xhr send define a method to parse the partial response chunk by chunk var last_index 0 function parse var curr_index xhr responsetext length if last_index curr_index return no new data var s xhr responsetext substring last_index curr_index last_index curr_index console log s check for new content every 5 seconds var interval setinterval parse 5000 abort after 25 seconds settimeout function clearinterval interval parse xhr abort 25000 the biggest problem with this method is that the responsetext property keeps filling up with data the longer you receive data the bigger the data in memory will be the only way i can see this fixed today is to simply kill the connection after a certain amount of data has been received and open it up again i would love to see a better way to do this from native javascript without all the numerous hacks that are out there if you know of a way that fills these requirements please let me know easy to implement on the client side ideally i would like to use xmlhttprequest and just get a callback each time the client sends data with the new data specified as a callback parameter easy to implement on the server side i can set some headers if you make me but ideally i would like to use this against existing streaming apis like twitter s without adding custom stuff as cross browser cross platform as possible is there a way to get this working it s so annoying to see something that s a curl one liner be 100s of lines of code with web technologies curl https stream twitter com 1 statuses filter json track your keyword u your twitter nick is the web really that far behind comments jan 8 2012 by emil stenström 1 one interesting idea is the multipart x mixed replace mime type http en wikipedia org wiki mime mixed replace_ 28experimental 29 may 25 2012 by mark 2 i tried your javascript against the twitter streaming api but i got the error origin is not allowed by access control allow origin have you found a way around this problem may 25 2012 by emil stenström 3 mark yeah you need a modified xmlhttprequest i used one from titanium