> Data is not to be tied to threads there but to actual iteration values, > because they can appear on the iteration channel in any order. That pretty much is my comment about how this does/does not map from the Swift to the Karajan layer - I think it does, but not in a way that a karajan purist would be happy with. --