[Dancer-users] Web-front end for long-running processes
gordon at cshl.edu
Thu Sep 20 18:27:05 CEST 2012
damien krotkine wrote, On 09/20/2012 11:58 AM:
> WebSockets !
Sounds interesting, I'll have to brush-up on HTML5-ism.
But this only takes care of the server-client side communication, not the unix process handling (I neglected to mention that users might close their browser window and come back to it later, expecting to see their jobs still running).
It seems Apache doesn't support WebSockets proxied to perl (at least I couldn't find any reference to that),
and "sudo cpan Dancer::Plugin::WebSocket" fails with too many errors (on Perl 5.14.2) - so I'm not going to pursue it ATM.
> On 20 September 2012 17:46, Assaf Gordon <gordon at cshl.edu> wrote:
>> I'm planning a web site (w/ Dancer, of course :) ) that will execute shell scripts (to compute some results) and eventually return the results to the user.
>> The web-side is simple enough, but the shell scripts might take anywhere between 10 seconds to 10 minutes to execute.
>> Is there a recommended way to manage external jobs for this type of scenario ?
>> One extreme is to use SGE/PBS and build a whole database-backed-up queuing system.
>> The other is perhaps to execute the shell scripts (serialized, one after the other) and just send the results to the users by email.
>> But if anyone has experience with something similar, any advice will be appreciated.
>> (This is supposed to be a short-term project, just a front-end to some unix scripts - so I prefer to keep it simple, not build a full-fledged infrastructure from scratch).
>> Dancer-users mailing list
>> Dancer-users at perldancer.org
More information about the Dancer-users