Hello, this is for Martin:
I am planning (that's a medium-term to long-term issue, nothing imminent) to update the qcl library and my two production apps to make use of recent and upcoming developments in qooxdoo regarding the virtual widgets (tree, upcoming table) and i/o (rpc, REST resources). I am very interested in what's ahead. In particular, I'd like to know how the new concept of REST resource will play with databinding - are there plans to link the two or will this be totally up to the developers? I have always been a fan of some way of "databinding-over-the-wire" which specifies a backend-protocol/API (to be implemented in whatever server framework one might use). The idea of a "resource" controlled by a REST "API" is very promising in this regard. The use cases of a table or tree are so similar (they work on a data model on the client and the server and create/read/update/delete records here and there) and it would be nice not to have to implement this logic over and over again, and instead concentrate on the access control (who is allowed to perform which CRUD operation). What's your take on this? C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/databinding-rpc-REST-resources-tp6655875p6655875.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
