Ben Alex schrieb:
I think it would be valuable if there was a high-level architectural
diagram showing the layering you had in mind for this project, such as
where XML is generated, parsed, data exchanged, JavaScript written,
and language-specific callbacks used. This would allow further
discussion not only about the technical approach, but also which
projects (Qooxdoo, PHP-Qooxdoo, Java-Qooxdoo etc) should develop which
layers and modules within those layers. I'd ideally like to see
server-side language usage minimised and kept as a very thin stub over
the XML with perhaps communication over an agreed protocol (I'm a big
fan of JSON-RPC as mentioned on this list in the past). If the
community can agree on the best technical architecture and layering
for Qooxdoo-specific server-side interoperability, I am happy to
assist with a Java port of the server-side code.
Hi all,
this is exciting. I agree with Ben. Let's define a protocol (preferrably
using JSON-RPC) and then let people create backends. How great it will
be if I can reuse the XML GUIs for several backends...
I would propose that a server should do the following:
- accept GET and POST requests,
- authenticate the user (with a standard user/password parameter),
- do basic security stuff (for example, prevent code injection in
parameters),
- convert JSON data in the parameters into native data structures
- call an named object and object method (for example,
"bibliography.getRowsBySql") - this could be a java object or a php
object - objects could also be template files which return HTML
- return data, indicating the mimegtype of the data (for example,
text/json, text/javascript, text/plain, text/html, x-application/xul,
text/xml, or what have you)
This requires a data binding class on the client side. Until the
QxTransport Classes are ready, there is dojo.io.bind() from the
dojotoolkit. This class would call
"http://www.server.org/qxserver.php?_procedure=foo.bar&arg1=['blub','blah']&arg2={first:'nee',second:34}&_dataformat=json"
or something like this. Are there specifications by JSON-RPC? There is
an implementation in the dojotoolkit.
Concerning the name: what about simply "QxServer"? I would, however,
always have dojo built in, too.
An XML - Format has already been defined by QxBuilder, I propose to just
take it over.
Also, the whole thing should be able to generate documentation with
doxygen.
Christian
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
