Yes, I think the building blocks for a lightweight architecture for an end-to-end qooxdoo application that communicates, in "real time" (that is, as fast as the transport allows) in both directions are all there, and simply have to be properly configured and made stable. What still misses, at this point, is encryption. If you skip Apache and fully rely on node.js as a server, you have to do all the encryption yourself. Which might be a crucial point.
Cheers, C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/RpcNode-taking-shape-API-Viewer-for-server-classes-tp5424073p5433126.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
