Hi Benoît, actually, what I have in mind is to replace Apache altogether for the node.js part. I have the feeling that small qooxdoo apps could do without Apache if a server script based on node.js can supply all the files that are needed for the initial loading of the client application, and then switch to an event-driven bidirectional socket communication with the server plus node.js-based json-rpc.
I think this could server as a complete out-of-the-box client-server solution. I have no idea if that would scale well, but for the kind of applications I of which am thinking, this seems to be a much better solution than resource-hungry Apache or other other backends. Any thoughts? C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5363466.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
