Hi, just to toss in my 2 cents: having used JSON-RPC w/ qooxdoo extensively in the past without any problems, I think that RPC is not the way to go. All the new development in qooxdoo has been gone towards REST and there are good reasons for that, because it is the "native" web app data communication. I'd say that to be future-proof, it is either REST or a bidirectional protocols such as websockets/socket.io (which are not very well supported by PHP, of course).
I haven't looked at your code in detail, but I saw something about "synchronous", and I think that synchronous JSONRPC is a bad idea anyways. Many problems in JavaScript arise arise when you try to avoid the asynchronous model. Once you embrace it, it becomes much clearer how the program flow is and why stuff doesn't work. But maybe you have done that, then disregard my comment. C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Need-help-with-Models-please-tp7581630p7581664.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
