Atmosphere/atmosphere — pull request #946 by flowersinthesand (2013-03-04 15:06:14+00:00)
Title: Partial update from 1.0 to 1.1.0beta4

This pull request contains the **partial** update between 1.0 to 1.1.0beta4. For details, see commits. Frankly, the current jquery.atmosphere.js is too much changed comparing to that of 1.0 to apply changes to atmosphere.js. New options like dispatchUrl and webSocketBinaryType are undocumented and there is no comment on added code. Of course, I try to find and understand a releated issue and commmits, but there is a limit to my time. Sometimes, even it doesn't help. https://gist.github.com/flowersinthesand/5072049

Besides, from the start, I still have been not sure about the big picture such as the life cycle and event in accordance with the state transition and so on. (The number of lines of code is bigger than 2500!) Accordingly, atmosphere.js looks unstable and experimental. This is a reason why I included jquery.atmosphere.js as an weakness. It's not easy to understand.

Anyway, we can solve this chronic problem by TDD like the portal did. For this, I added an web app running atmosphere.js test suite to the module. You can execute it by `mvn jetty:run-war`. It doesn't affect the result war of the module for sure. Resources are in `src/test/webapp`.

To do

1. synchronize document with the current jquery.atmosphere.js including all the available options, properties and methods. The document about the life cycle is also recommended. https://github.com/flowersinthesand/portal/wiki/Socket-Life-Cycle-and-Events
1. **write test cases to test.js and the server if needed according to documents**

I know you don't have the cycle, but at least, to make atmosphere.js solid and easy-maintainable, you should write test cases. You don't need to implement atmosphere.js. It can be done by me or other contributors. It might be better to start with empty test.js.

Thanks,