Well, if you're in LPS 3.4, obviously your using the Flash runtime...
so, I think you might want to use the same underlying primitive that
the LzDataset is using, which is to use the Flash XML object, and call
it's sendAndLoad method, and then write a callback for it which grabs the
raw data
from the response.

If you set up the flash onData callback on your XML object, you get a string
back which is the raw data, before it has been parsed.

You can look at the actionscript docs to see how that works.

http://www.adobe.com/support/flash/action_scripts/actionscript_dictionary/actionscript_dictionary827.html

http://www.adobe.com/support/flash/action_scripts/actionscript_dictionary/actionscript_dictionary856.html

The XML sendAndLoad method works like the LoadVars.sendAndLoad

http://www.adobe.com/livedocs/flashmediaserver/3.0/hpdocs/help.html?content=00000325.html

Sorry there isn't anything better for 3.4...


On Fri, Jun 19, 2009 at 3:47 PM, jgo <[email protected]> wrote:

>
> I see in the docs that dataset is the standard way to make POST requests,
> but
> that is if I want to get raw data back to be used within the Laszlo app.
>  In
> this case, I want to get an actual CSV file that the user will download to
> their computer and import into Excel.  Am I missing something with dataset
> that will allow me to do this?
>
> Unfortunately, the move away from 3.4 is not possible due to a combination
> of code and internal reasons.
>
>
>
> Henry Minsky-2 wrote:
> >
> > Oh, I see you said you're using LPS 3.4, I don't know if the rawdata
> > option
> > was
> > implemented at that point. You may need to move up to a more recent LPS,
> > or
> > use another method to get the rawdata (such as making a low level Flash
> > sendAndLoad or XMLHTTPRequest call)
> >
>
> --
> View this message in context:
> http://www.nabble.com/how-do-I-post-a-request-to-a-CSV-generating-servlet-from-within-Laszlo--tp24116357p24117737.html
> Sent from the OpenLaszlo - Dev mailing list archive at Nabble.com.
>
>


-- 
Henry Minsky
Software Architect
[email protected]

Reply via email to