3 ms·
I never had a problem with this. The protocol I wrote just sent a job-ID to the client and the client started polling for the result. Since AJAX is already as
by k__ 13y ago
I never had a problem with this.
The protocol I wrote just sent a job-ID to the client and the client started polling for the result.
Since AJAX is already asynchronous I could write a JavaScript library for the browser, which made the whole thing transparent for the client.
The only problem I ran into were multiple long running jobs, which caused parallel polling. But since the communication between server and client was hidden behind the client-lib, I could change the protocol later, to merge multiple polling requests in one etc.