Can't run the pure JavaScript client on node.js due to "window" references about atmosphere-javascript HOT 5 CLOSED

I'm not sure why the readme.md contains that info, but anyway atmosphere.js is not compatible with node.js. Considering socket.io-client and engine.io-client, it looks like a time-consuming task to make it node-compatible.

Maybe, we can add this feature after a release of Atmosphere 3.

Just for your information, there is an article about Atmosphere and node.js: http://jfarcand.wordpress.com/2013/04/04/wasync-websockets-with-fallbacks-transports-for-android-node-js-and-atmosphere/

from atmosphere-javascript.

Hum it has been awhile since I tested node.js...I was under the impression no user. Will take a look, but I'm not sure it can be fixed :-)

from atmosphere-javascript.

Thanks for the explanation :-)

I suggest taking it out from the following, to avoid future confusion:
https://github.com/Atmosphere/atmosphere-javascript
http://async-io.org/release.html

from atmosphere-javascript.

To be fixed following flowersinthesand/portal#115

from atmosphere-javascript.

I created a repository for this.
https://github.com/flowersinthesand/atmosphere.js-node

When releasing next version, I'll publish it to npm under the name of atmosphere-client. As its readme say, there may be difference from browser and it's not easy to check it since there is no test suite for client. Please test it and open a bug if you found.

/cc @rubyboy

from atmosphere-javascript.