[Swift-devel] The method getting result back

[Mihael Hategan]

Swift already uses lightweight threading. There is a limited number of
OS threads that do the work.

On Mon, 2008-04-07 at 09:15 +0800, jezhee wrote:
> After the tasks are dispatcjed to the computing nodes, what should swift do? Now, it simply blocks and waits until the tasks are completed and send the result back. It's suitable for the light-weighted tasks or the situation swift handles a few applications. When Swift runs as a server for several applications, simple block will lead to waste and inconvenience.
>  In the future version, I think this work should be done by a independent thread running as a demon. When the tasks has been transfered to the computing grid, the main thread switched the work to this thread. This thread will do the left stuff. Even for the simple application, there is no harm too.
> 　Jezhee
> 							2008-04-07
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel