Viewing profile — joombar

I realise not the usual format for a story. But to Gawk... in this world of zero downtime deploys this is remarkable. As the sun rises in the UK, this is half the business shut dow…

"And they're right- a boy who enjoys t-shirts and sports is at a tremendous social advantage over one prefers dresses and ballet" Perhaps in some very conservative societies. Where…

For small messages it will be slightly slower in terms of CPU time because of JS vs native DOM parser. But for small messages the time taken with modern JS engines should be less t…

Two different user agent strings for one version of one browser? That can change at any moment based on a list the site authors don't control? There's no way that'd ever confuse th…

Just merged in support for reading any stream in Node: https://github.com/jimhigson/oboe.js#reading-from-any-stream... oboe( fs.createReadStream( '/home/me/secretPlans.json' ) ) .n…

Well, you could have a JSON which was valid at the start and invalid at the end. It'd parse the first bit ok and only throw an error when it got to the invalid bit. Nothing gets pa…

No, although that's a nice idea and something I'd like to look into.

Do you know how to do that from node? Here's the little test service I wrote to stream out some gzipped content: https://github.com/jimhigson/oboe.js/blob/master/test/stream...

In meantime, made a bug report: https://code.google.com/p/chromium/issues/detail?id=309092

Quick experiment says: Gzip can be written out as a stream ok. Can't comment on Apache but Node does it fine. Firefox's xhr fires progress events for gzipped content but not Chrome…

It should make most calls faster. Exceptions are for small JSON files or on networks that are fast enough there is no streaming effect (the whole file arrives very quickly) For mos…

it is built on top of a sax parser.

Liable to change but "An approach to i/o for rest clients which is neither batch nor stream; nor SAX nor DOM." I'm writing it now.

I suppose you could make a binary equivalent if you needed to. You'd need to make some kind of binary matching language, maybe like Erlang's binary matching. Adding XML/XPATH suppo…

There's only a node side so far as I needed to write for some component tests. It'd work with anything that writes out valid JSON. The client side works in Node right now as well a…

If you don't care about old browsers you could use the same connection to keep the state updated as you used to download the original state. I built this for more-or-less standard …

I haven't looked at MXHR but here's roughly what Oboe does: 1 Create XHR, listen to XHR2 progress event. 2 Use Clarinet.js SAX parser, scoop up all events. 3 From SAX events, build…

Hadn't seen that before. Interesting link, thanks. Very similar except JSON/JSONPath instead of HTML/CSS. Oboe runs fine in Node but I want to make the code a bit more standards-y.…

I agree. If you're doing something slow/asynchronous like aggregating several http resources it is worth it to write out as early as you can but keep server-side the same if you ca…

Hmmmm, yeah. Use cases doesn't take up much space, I'll put that before examples because it explains better what it is for.

There's a cool thing you might try where you can download the historic messages, then continue to stream live ones over the same http. If you don't care about old browsers (anythin…

I'll have to test to be sure you still get streaming. It depends how the browsers handle xhr2 events with regard to gzip'd http. I /think/ it'll be fine but I need to check to be s…

Should be fixed now. Thanks for pointing out. There's a test explicitly for not allowing this: https://github.com/jimhigson/oboe.js/blob/master/test/specs/...