I am looking at the new qx.io.request.* classes to consider converting my
RPC simulator to use it. I am unable to determine, though, how the selection
of a transport is accomplished. In the old implementation, one instantiates
a qx.io.remote.Request object and sets a number of "needs" such as async or
not, expected response type, cross domain or not, etc. Those high-level
needs determine, at a much lower level, which transport is to be used
(XmlHTTPTransport, ScriptTransport, IframeTransport, or a transport added by
the user, such as the simulation transport). The new implementation seems to
be lower-level, leaving the selection of the transport up to the caller. Is
there a higher-level class that has not yet been written? What are the plans
here?
Derrell
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
