Ease of configuration should be a hosted solution that uses WebSockets, streaming HTTP or HTTP Long-Polling (one of which I work for). This is the easiest option, because you do not need to spend time installing your solution, setting it up and developing how to use it in development and production.
If you are looking for a stand-alone solution , then it really depends on the technology that you prefer to use, and how the community is similar for this technology.
- Node.js and socket.io has a large community, the following at the moment, so this would not be a bad choice.
- PHP I am afraid that PHP is not really built with long standing connections. Thus, while there are options, it is probably best to use either a hosted service or to avoid it.
- Ruby - check Faye (there is also a node.js option), Juggernaut or Cramp
- Java: As you say, jwebsocket or WaterSpout Server
Hope this helps.
source share