I've used something along these lines in the past for a medical imaging app. We needed to pre-fetch images and possibly pre-process them (filter, apply overlays) so that as a user was scrolling through an image set it was smooth and they weren't waiting for images to be processed. The GUI handler thread would figure out what images were supposed to lie just above and below the current viewport, then it would put tasks onto a queue where worker threads would pull them off and process them as fast as possible.
That's one example anyway. On Mar 2, 10:56 pm, Jonathan Mitchem <jmitc...@gmail.com> wrote: > At the risk of sounding incredibly uneducated about the matter (oh wait, > it's true): > > What is the purpose/need/reason for this kind of architecture? What can you > do with it? Where would you use it? Why would you use it? > > Thanks, > Jonathan -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
