The general concept is outlined very well in Watching long-running processes through CGI.
My suggestion is that you read this article and then implement it.
As you don't tell us where exactly you have problems, my suggestion is to first eliminate all the Javascript from your approach and implement the solution in the linked post. After you got that working, you can easily add Javascript again to update parts of your page instead of reloading the complete page.
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |
That's a follow up to send mail ?
Most likely, yes. bigup401 has a long trail of abusing perlmonks as a free (as in beer) code writing service. To me, it looks like a single job rotating around a multi-language web application that needs to mail some stuff and use the Paypal API, accepted by someone who has not the slightest idea of how all of that could ever work. bigup401 has proven several times to be unwilling to learn, unwilling to answer questions, unwilling to show a minimum of efford when writing postings. For me, it's just a waste of time to answer postings of bigup401. That time is better spend answering questions of people showing at least a tiny bit of effort, and are willing to learn just a tiny bit.
Update, 2020-Dec-20:
eyepopslikeamosquito++ sums up, compares to the worst monk so far, still trying to help in Re^5: joining words. I doubt that will change bigup401's behaviour in any way.
Alexander
--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |