>>> Took me a while to see what is wrong. :-) WSAPI has to wrap your
>>> application inside a second coroutine to get isolation (see
>>> wsapi/ringer.lua), and transforms wsapi.input:read into
>>> coroutine.yield("RECEIVE"). That is why you are seeing "RECEIVE" in your
>>> response; wsapi.ringer is never getting this command and never sending the
>>> data back.
>>> I think I can fix this bug, but for now the workaround is to move
>>> wsapi.request.new outside of the iterator (just after you declare the
>>> headers variable, for example).>> Fixed in my last commit: >> http://github.com/keplerproject/wsapi/blob/1ab57272935224a31022a502db84881b8f24ab0c/src/wsapi/ringer.lua > Wow! Thanks! I'll check tomorrow if this fixes the issue. Fix confirmed, thanks again! It seems that I've won the battle with luarocks. So I'll check out the rest of fixes tomorrow. Alexander. _______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
