Oboe.js: reacting to Ajax/Rest quicker by not waiting for it to finish

Re:Oboe.js: reacting to Ajax/Rest quicker by not waiting for... by jastanton on Friday October 18, 2013 @10:52AM (#6571673)

So if you're streaming in the JSON this program must have a custom JSON parser because there would be no way to assure valid JSON on an incomplete payload. Am I understanding how this works correctly?

edit: Also how is this faster, if you're parsing an incomplete response over and over again isn't each parse blocking, wouldn't this approach kill your FPS?

[ Parent | on HN ]

Re:Oboe.js: reacting to Ajax/Rest quicker by not waiting for... by joombar on Saturday October 19, 2013 @06:09AM (#6575931)

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 parsed more than once. SAX parsers already parse streams, they're just not used very much because they're a pain to program with.

[ Parent | on HN ]

Re:Oboe.js: reacting to Ajax/Rest quicker by not waiting for... by the_gipsy on Friday October 18, 2013 @12:33PM (#6572264)

Yes, it uses SAX which seems to fire events as nodes get parsed. I don't think that the response, or any node of the JSON string of the response, gets parsed more than once.

[ Parent | on HN ]