Improve Computation Layer to operate on current generation

[GoogleCodeExporter]

Right now the Computation Layer can only operate on the generation behind the 
current one, as it attempts to ensure nothing is writing to the generation it 
processes (or else data is lost). There are better ways to manage this, such 
that the CL can wait for Serving Layers to switch to a new generation and then 
run the current generation. This will lower latency by one cycle.

Original issue reported on code.google.com by srowen@myrrix.com on 8 Oct 2012 at 12:48

[GoogleCodeExporter]

Fixed for 0.8. It will create a new generation, wait for migration to the new 
generation and run the (recent) generation that data was being written to as 
the next computed generation.

Original comment by srowen@myrrix.com on 17 Oct 2012 at 7:00

• Changed state: Fixed