tag:blogger.com,1999:blog-29331675.post7935033696502189237..comments2024-03-05T17:37:00.995+01:00Comments on The Delphi Geek: Generating Reports with Background Workergabr42http://www.blogger.com/profile/06903558857617342477noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-29331675.post-25197233484805700952013-01-17T11:50:54.927+01:002013-01-17T11:50:54.927+01:00Destroy workers on the 'destroy' list (Cli...Destroy workers on the 'destroy' list (Client1) never appears<br /><br />Calling a cleanup when nothing is running may solve that ?<br /><br />procedure TReportGenerator.Cleanup;<br />begin<br /> ProcessDestroyList('');<br />end;<br />DelphiMagicianhttps://www.blogger.com/profile/00329937331782780093noreply@blogger.comtag:blogger.com,1999:blog-29331675.post-8092053925257125472012-10-24T18:48:54.131+02:002012-10-24T18:48:54.131+02:00That was a fun one!That was a fun one!ObjectMethodology.comhttp://www.objectmethodology.comnoreply@blogger.comtag:blogger.com,1999:blog-29331675.post-23232569473820153052012-10-23T20:53:32.091+02:002012-10-23T20:53:32.091+02:00This sounds like a job for a database, a service a...This sounds like a job for a database, a service and background processes. With background processes there would be no threaded hassles as some report writers are not thread safe, errant processes won't hose the main service, there is built in clean up when the process is finished as it will exit memory and the system could easily scale across multiple servers if needed. Cameronhttps://www.blogger.com/profile/12643798206251661265noreply@blogger.com