|Originally posted by *Calsy|
Hi All, Ive been reading the DevForce Developers Guide and am currently looking at the section on threading. The section keeps on saying when you shouldnt use threading. Just wondering what are the situations where multi threading should be used and will have the biggest advantages (over asynching)?
Between async queries and async remote method calls (made using aPersistManager.InvokeServerMethodAsync()), you can cover quite a chunk of the use cases that might otherwise motivate you to do your own multi-threading. I suppose any time-consuming process that you can't address satisfactorily with either of those facilities, and which has a sufficient impact on your application's performance to make it worth your while to delve into multithreading, would be a candidate.
We had at least one customer, for example, who needed to do saves of sufficient complexity and volume that they felt they needed an asynchronous save. It does raise issues (of recovering client-side if the asynchronous save fails) but they wanted it anyway.