Assuming you're not doing some ajaxy thing, you need to block on the main thread until all of the other threads complete. Set up some wait handles, kick off the threads, have them signal the handles when completed and have the main thread wait on them all (or time out).
-----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Peter Vertes Sent: Monday, January 08, 2007 2:21 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: [ADVANCED-DOTNET] Threading in ASP.NET *Hello List,* Happy New Year ! I'm having some difficulties with threading in ASP.NET. I'm working on an ASP.NET app that upon Page_Load() goes out and does WMI queries on a number of remote machines to retrieve their status at that moment. When I'm not using threading and and performing these queries one after the other (asynchronously) everything works great. I get a snapshot of the remote machines back but it takes a while (about 30 seconds) to generate the page. Since this application would be the perfect candidate to speed up up using threading I sat down and added the threading code but for some reason my threads seem to be terminating before the WMI query is back with results. The only way I can retrieve useful results is if I implement a busy wait inside my code and hope that all the WMI queries come back before the busy wait completes. Since this is my first attempt at using threading within ASP.NET I assume I'm missing someone. Could anyone give me a hint as to what I'm doing wrong ? Thanks in advance... -Pete =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
