I have to admit - closures in ColdFusion 10 were not terribly exciting to me. Don’t get me wrong - I’m really happy they were added. Much like I was happy the engineers added implicit notation and other “syntax sugar”. But it’s not really a “feature” per se. It’s there - I’m happy it’s there - and my brain will just mentally keep it in mind as I write ColdFusion.
That was how I felt before cfObjective. Then I attended Mark Mandel’s session on Closures and he opened my eyes to the possibilities. Specifically, he demonstrated his Sesame library - a set of closure-based utilities you can include in your projects. Simple, but nice things like…
Nothing too revolutionary (and parts of Sesame are based on things found in Groovy), but seeing them in action really made me appreciate the support of closures a lot more.
Things get real interesting though when you look at the concurrency aspect. ColdFusion added threads a while back. They are a powerful, if somewhat dangerous, addition to the language. Running code in a thread and ensuring you properly handle the end result can be tricky. Until you try Mark’s code:
In case it isn’t obvious - the _eachParallel function runs once for each item in the array and fires the code concurrently. My closure runs a sleep function which will slow down the processing of the page. But since the closures run concurrently, you will only have to wait for the slowest one (5 seconds) and everything else will be complete. Here’s a screen shot of the output from that sample: