This post originated from an RSS feed registered with Java Buzz by Weiqi Gao. Original Post: SwingWorker, Secondary EventPump, JIT Cache Bwtween Runs, ... Feed Title: Weiqi Gao's Weblog Feed URL: http://www.weiqigao.com/blog/rss.xml Feed Description: Sharing My Experience... Latest Java Buzz Posts Latest Java Buzz Posts by Weiqi Gao Latest Posts From Weiqi Gao's Weblog

Sun has posted the transscript of a SDN Chat Session about Desktop Client. The parts I liked the most are:

JavaGeek: Why hasn't the SwingWorker (or a similar mechanism) made it to the standard APIs? What is the recommended way to deal with process-intensive tasks?

Scott Violet: Excellent question. It turns out we're very close to finishing up a version of SwingWorker that will be part of 1.6. This is the version that Igor, Brent, Bino and myself talked about at last year's Java One conference. This version of SwingWorker is generified and supports property change listeners. It's extremely handy. I'll also mention that AWT is looking at a way that you can pump events during a long running process. Other toolkits provide similar mechanisms and it turns out it's very handy.

markyland: Are there any plans to allow Swing applications to be compiled natively?

Scott Violet: The closest thing I can say we're looking into is persisting compiled code between runs of the JVM. For example, each time you run your application we end up compiling a lot of the same methods; if this were cached it could conceivably speed things up. Whether or not something like this makes it in depends upon the results we get.