David, You'd want to use some sort of AJAX background process to check a status flag, instead of constantly refreshing the browser page.
Once the report is generated and available, then you can replace the "waiting" with "available" and a link to the file. sincerely, mehboob alam Electricity is actually made up of extremely tiny particles called electrons, that you cannot see with the naked eye unless you have been drinking. - Dave Barry ----- Original Message ---- From: David Ringsmuth <[email protected]> To: [email protected] Sent: Monday, July 6, 2009 1:58:21 PM Subject: [Active4d-dev] Web Application Deployment Assuming HTML and Javascript, CSS, are the primary technologies, when web-ifying a 4D Client application including the delivery of reports, what is the preferred method for delivering to the client complex reports? I can imagine a user interface where the report is defined and requested, then a link is dynamically created pointing to the newly created PDF report, and the browser refreshes until this PDF is "available". When it is available the user selects it for viewing, etc. I imagined processes created on a 4D server to handle the report creation. Does that sound workable in an environment with hundreds of simultaneous web users? Thanks, David _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/ _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
