Hi,

I would do that on the server side.
Launch the server "export to excel" in a thread that you monitor on the server 
"entrance".
In case of time out, destroy the thread (an clean the resources : files, ...) 
and build a response that a time out occurred.

=> nothing to change on client side.

This way, you won't have to mix 2 different time out :
- the one for client-server dialog
- the one for the excel export

Hope this helps.

On 11 oct. 2011, at 23:51, Fink, Andreas wrote:

> Hi all,
> 
> I have some reports in my frontend that gets data from a Java backend.
> The users have a function to export the reports data to excel files.
> My problem is, that if the there is a huge amount of data in such a
> report, this export function could take very long.
> 
> Is it possible to create something like a pending call? 
> If a timeout occurs the call should not be automatically aborted,
> instead I want to ask the user if he want to wait another amount of time
> or if he want to abort the request.
> 
> Regards,
> Andreas
> <winmail.dat>------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct_______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to