>
> * serve a delayed response to a client (like a result of a db query)
> * maybe run some things on a server, while a client can pull job
> status, and render results?
I did implement something like this - but in reverse. client uploads a large file and it gets processed on server chunk by chunk and sent back to the client.
I am not extremely happy with it, and the tests aren't complete but it seems to work (uses fork)
https://github.com/hitz/RegulomeDB
Following on the discussion from last week, I thought it could be reimplmented with WebSockets using something like this:
http://mojolicio.us/perldoc/Mojolicious/Guides/Cookbook#Streaming_multipart_uploads
But there are two issues with that:
1) I wanted the client to be able to close the webserver and get the results later
2) Project is currently not funded, and hence somewhat deprioritized.
Ben
--
Ben Hitz
Senior Scientific Programmer ** Saccharomyces Genome Database ** GO Consortium
Stanford University **
hi...@stanford.edu