Hi Fabian,
Fabian Jakobs wrote: > > We are using NGINX as reverse proxy. NGING handles SSL encryption and > serves static files. All other requests are forwarded to node.js. > hm, but I am thinking of the opposite scenario - I don't really care so much about the static files (== the qooxdoo application), they can go unencrypted to the client. What needs to be encrypted is the data that gets sent with the message-passing and rpc system... I now understand the value of SOAP - but I don't want the overhead of SOAP, I want to stick with simple node.js/json, but prevent others from intercepting sensitive data... C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/RpcNode-taking-shape-API-Viewer-for-server-classes-tp5424073p5436724.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
