Hello, I'm nearly finishing my first qooxdoo/websocket-powered app but I'm still wondering some general questions about websocket usage.
My app consists mainly of an interactive qx.ui.table.Table where clients can perform and see changes in real-time thanks to websocket. For the moment, only the updates operations and alerts are send via the websocket protocol. The others "queries" are still in pure ajax. For instance, loading datas (using a custom remote model) and importing datas (using xls files and hidden iframes) are still ajax requests because I'm worrying a bit about general performance. I don't know exactly what is the impact of making long-running and "not-resources-friendly" commands via websocket. I know that there are no length limits on send and response messages but I'm a bit afraid of letting clients importing big datas files via the websocket protocol. So, for the moment, whenever this kind of operation is done, I make a request via websocket to analyse changes in the database to order to limit the length of the response message and avoid long-running threads. But maybe there is nothing in my "fright" actually. This kind of operations should be manageable without any big latency and too much memory consumption on the server. To sum up, I don't know exactly what is the best option in this case. Any suggestions according your experience ? Best, Benoît. -- View this message in context: http://qooxdoo.678.n2.nabble.com/html5-question-about-websocket-usage-tp5569725p5569725.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
