gistfile1.js

/* 
 There once was a server-side stream eating function which looked like this:
*/

Meteor.startup(->
  Crawler.Stream.create(sources).on('readable', ->
    stream = this

    while item = stream.read()
      /*
        And this is where things go wrong: although Fibers allow async
        programming in a sync-style, it means execution is halted here
        and the next item is only read after store()'s async operations
        are completed.
        */
      store(item)))
      
      
/*
  And our store() function has a collection update
  */
store = (item) ->
  MyCollection.upsert(item)