w00t, we committed this as r4145! We did make a few changes to it: - Passing serialized ASTs around is gimpy, we just pass the UnifiedAst; it can handle memory management internally. This actually allows the main process to reuse the original Ast.
- We flipped things around such that the caller actually passes a corresponding set of result files into the PWF. This prevents having to do the temp-file-then-copy trick with CompilePerms. I still want to go back at some point and implement the "generic file-backed serializable thing" concept which would make this even cleaner. - Fixed a few bugs. - We ended up going with Lex's ThreadPoolExecutor stuff. Mainly because he was physically here, and I think both of the TPE-based implementations suck. :) Tomorrow we need to check the build machine for a successful 1.6 build, and then merge up to trunk so you can merge in SOYC. Scott --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
