Obviously, you might try to write algorithms that operate as normal iterators. I would be avoiding the multi-thread model if possible. The yield approach I guess if for cases where this isn't practical.
I was thinking that you could even use this as an aggregator for multiple threads. For example, multiple HTTP service threads could all be delivering objects to a single iterator, which iterates forever, processing the results on a single thread. On Oct 13, 8:50 pm, Casper Bang <[EMAIL PROTECTED]> wrote: > Very cool, continuations is another thing we need to bring down > ceremony and housekeeping in Java. I would think your impl stands a > better chance at being adopted into Java than Aviad Ben Dov's Yielder, > although I am not sure about the (performance?) drawbacks of either > over native support. > > /Casper > > On Oct 12, 11:20 pm, "Jim Blackler" <[EMAIL PROTECTED]> wrote: > > > Hello all > > > I've just finished a little library and article about my efforts to > > emulate a form of C#'s yield return in Java. > > > It uses a new thread and a SynchronousQueue object to enable any > > calculating function to return its output through a standard Java > > iterator. > > > The post is here ..http://jimblackler.net/blog/?p=61 > > > I'd be interested in any views. > > > Jim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
