On 15/11/2010 14:42, Derrell Lipman wrote:
On Mon, Nov 15, 2010 at 07:59, Joffrey Fuhrer - NOVLOG
<[email protected] <mailto:[email protected]>> wrote:
On 12/11/2010 19:45, Derrell Lipman wrote:
> 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
Actually we find ourselves kinda stuck and out of options here,
so I'll try to give some details in order to have your suggestions;
What we're trying to do is send a file to the user, but the content
of the file will depend on information that is contained in the client
application.
In other words : we want to send a CSV file containing the information
gathered in a qooxdoo table.
I've ended up choosing to use the Iframe class because with the
qx.io.remote.Request class as well as the qx.io.HttpRequest class,
the servlet response is "captured" by qooxdoo, while we want the
browser to process it as a file.
Knowing this, is there anything in qooxdoo that could fit our needs
better than that?
If not, is there any guarantee that code written with this class
will be maintainable, or are we really in the qooxdoo jungle
there? =)
Hi Joffrey,
You didn't reply to the original message, and didn't include any
context from the original message to remind me what we had discussed
originally, and I read and respond to too many messages to keep them
straight in my head, so I'm working with very little information here...
I don't understand what you mean by "the servlet response is
"captured" by qooxdoo. And what does it mean for a browser to process
something as a file? The responses to all requests by an application
are returned to the application, and the application can do what it
wants with them. If the response is CSV data, then it should be sent
as text/plain and the browser can do with it what it will, right.
I'm missing something here, I think. Sorry I can't be more helpful
here, but I don't understand the scenario you're describing? If you
provide more details, I'll try to help. Be sure to reply to this
message, and keep the context intact.
Cheers,
Derrell
Hi,
Sorry about the mixup, I was not sure whether to start a new thread
or not and tried something a little in between, but it ended up
quite unclear.
By saying "process something as a file", what I really meant in this
particular use-case is that I want the browser to trigger a download.
The problem I encountered when trying to use qx.io.remote.Request was
that the browser I used was never made aware of this CSV file I was
sending back; and as I understand it, the content of this file was
probably "captured" in the "Response" object - which is what I
don't want because then I don't know how to output something as a
file in JS : in fact, that is why we do a server call.
So basically the idea is what I tried to summarize in the title of
this thread : I want to trigger a file download from a qooxdoo app,
using as much "qooxdoo magic" as possible, but without having my
app put its hands on the server's response.
Thanks for the time you're taking to answer this,
--
Joffrey Fuhrer
NOVLOG Intern
------------------------------------------------------------------------------
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
