4 ms·
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 F
by joombar 13y ago
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 up actual JSON and maintain path from root to actual node.
4 Match that path (+ some other stuff) against registered JSONPath specs.
5 Fire callbacks if they pass.
- k3n 13y agoInteresting. After looking at the MXHR more, it appears as though it was adapted from Digg.com[1] (aka DUI.Stream[2]), and then later adapted by Facebook[3]. Yours sounds more elegant in that it can handle JSON naturally, but I wonder if the other might be better suited for binary content (not sure in which context that would make sense, if any). Either way, I find them all fascinating, and I've starred your project :) Will keep an eye on it. 1. http://techfoolery.com/mxhr/mxhr.js http://techfoolery.com/mxhr/mxhr.js 2. https://github.com/digg/stream https://github.com/digg/stream 3. https://www.facebook.com/note.php?note_id=183263890703 https://www.facebook.com/note.php?note_id=183263890703
- joombar 13y agoI 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 support would be a natural extension.
- stuaxo 13y agoAwesome, I've been waiting for a library exactly like this :)