A quick glance at the play2 framework suggests to me that this is comparable with having a .net MVC solution as backend. In both cases, on the server side you just have one view, which is the qooxdoo app. The qooxdoo app communicates with the server side controllers, which are in this case functioning as services. In my .net mvc I have the qooxdoo front ends (one for desktop, one for mobile) in separate folders, and what I can tell, in your case these could be put in the public folder. But you could also put the app in an entirely different folder, not that you might then use JSONP to avoid cross domain calls.
You can then either implement communication with the server side controllers using a RPC approach or calling them like a REST service. To use the RPC approach you'll need to map the calls on the client side to the correct controller/action. Hope this helps. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Play2-framework-qooxdoo-best-practices-tp7586751p7586755.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
