David_W (70) [Avatar] Offline
The use of the worker object might surprise people who had other aspects involving cflow pointcuts due to cflow's use of thread local vars. Also, any changes made by the caller to parameters or state might have threading issues. For example, the original semantics of the included source probably assume that changes may be made to the project once the ProjectSaver.backupSave() method returns. This is no longer valid once backupSave is being run in a background thread.
ramnivas (171) [Avatar] Offline
Re: worker object comments
This is an issue async routing with/without worker object. It is just that the worker object pattern makes it easy, but one needs to consider the points you raised anytime a request is being routed asynchronously.