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 zamalek on Friday October 18, 2013 @10:00AM (#6571386)

This seems like it could be used to create a protocol similar to XMPP - which I always enjoyed from the perspective of elegance.

I might have a pet project this weekend, thanks for sharing.

[ Parent | on HN ]

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

No worries. This is my masters dissertation btw.

[ Parent | on HN ]

Re:Oboe.js: reacting to Ajax/Rest quicker by not waiting for... by alessioalex on Friday October 18, 2013 @11:17AM (#6571829)

What exactly is the title of your dissertation? (just curious)

[ Parent | on HN ]

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

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.

[ Parent | on HN ]

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

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 (anything without xhr2 progress events) should work fine to download and stream on same connection.

[ Parent | on HN ]