Oboe.js: reacting to Ajax/Rest quicker by not waiting for it to finish
This looks really cool!  I'm confused about the usecase, however.  In your foods/nonfoods example[0], it allows you to request a some JSON with 2 keys, `foods` and `"nonFoods"`, each with an array value, and use only foods, discarding nonFoods.  You request this from oboe('/myapp/things.json')<p>My question: why not modify the backend to accept a request like `/myapp/foods.json` and let the backend compose the json you need & send only that?  It seems like fixing it "in the wrong place" to build your frontend to accommodate getting the wrong/too much data.  Is this a contrived example that isn't the core usecase?  This is my assumption.<p>Is this primarily for 3rd party APIs and legacy codebases where it's impractical to change the response type & updating to e.g. sockets is impractical?  Thanks for the cool project, I apologize for my ignorance wrt whatever points I'm missing!<p>[0] <a href="https://github.com/jimhigson/oboe.js#using-objects-from-the-json-stream" rel="nofollow">https://github.com/jimhigson/oboe.js#using-objects-from-the-...</a>