On Fri, Nov 12, 2010 at 13:06, Joffrey Fuhrer - NOVLOG <
[email protected]> wrote:
> Hi list,
>
> We're currently implementing a new functionality in our app that behaves
> like a download (we want to serve a file to the user) but isn't really
> fetching a file on the server. For this purpose, doing a request to a
> servlet using the Iframe class seemed like a good idea even though the API
> advises against it ("This class should not be used directly by client
> programmers.").
>
The warning should be heeded. There are many interactions between the
(considered to be private) transport classes and the
qx.io.remote.{Request,Exchange,Response} classes. Once you find the solution
to your current problem, you may well encounter others because of those
interactions. You're pretty much on your own if you insist on accessing the
private classes. I'd recommend that you use the public qx.io.remote.Request
class to issue your requests. When you use qx.io.remote.Request, you don't
specify directly which transport to use. Instead, you specify a set of
requirements that must be met, e.g. whether this is a cross-domain request,
whether you need form fields, etc., and an appropriate transport is selected
for you.
If you describe in more detail what request you want to issue and what
you're trying to accomplish, we may be able to better direct you.
Derrell
------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
