Nice idea. If Flotype inherited NowJS' concept of one namespace for both server- and client-side it's a very smart thing built on NodeJS. I am sure there're t

Nice idea. If Flotype inherited NowJS' concept of one namespace for both server- and client-side it's a very smart thing built on NodeJS. I am sure there're tons of companies who would love to get a out-of-the-box real-time communication system w/o going too deep into node.js (which is btw perfect for this job). The idea behind nowjs is great but still isn't that trivial—your code has to be build around their core concept and at the end of the day you are pretty dependent on one sole company for core functions such as communication for your product. Further, there's is more to consider (are messages saved, if yes at flotype or do I have to build my DB and so on) and you quickly face the make or buy decision because with taking NodeJS and building your own communication stack on top. I want just to say that an integration with Flotype is more than just adding a one-liner—correct me if I am wrong—and currently it's too risky to rely on a new product which future is unknown. The point or what I am feeling uncomfortable with is that it's just proprietary tech. I think Sri will solve this issue (maybe with a freemium model where also the sources are under a public license and you pay money just for the servers)