Misleading JSGI Promise Docs

[James Cook]

In the Promise docs, there is an example that I don't think works under any circumstances.

https://github.com/ringo/ringojs/blob/master/modules/ringo/promise.js#L26-L34

exports.asyncAction = function(request) {

  var response = new Deferred();

  setTimeout(function() {

      response.resolve({

          status: 200, headers: {}, body: ["Delayed"]

      });

  }, 1000);

  return response.promise;

}

I don't see any code that would allow a promise to be returned to any of the JSGI methods and be able to handle it. In fact, I would really like this to exist. I was hoping I could just 'yield asyncAction()' to get the result, but that doesn't seem to work with this version of Promise. 

It seems like this behavior bugged me quite a bit 3.5 years ago also.

[James Cook]

Just like 3.5 years ago, I was able to synchronously wait for a WorkerPromise to resolve. This will let me run asynchronous code inside my application, but still allow my stick middleware to handle the response. But it is really ugly.

function handleWorkerPromise ( request ) {

    var wp = new WorkerPromise ( module.resolve ( './nls_worker' ), { request: request }, true );

    wp.wait ( 5000 )

    var result

    wp.then ( function ( payload ) {

                  result = json ( payload )

              },

              function ( error ) {

                  result = error

              }

    )

    return result

}

Furthermore, if my application code needs to yield for a promise (promise.wait() seems to be the only way to do this in Ringo), I will have to repeat this exercise for each of those types of interactions, and that doesn't seem very friendly.

[Philipp Naderer / Botic]

Hi James!

I filed an issue on Github: https://github.com/ringo/ringojs/issues/357 My hope is to fix it in the next days, but since we have the third attempt to elect the Austrian President early December it could take a little bit to look at this topic.

Bye

Philipp