I create a custom thread pool at app startup in an ASP.NET app (thanks to Mike Woodring) for long-running async processes. The thread's output (a dataset) is serialized to disk and then picked up by the original calling ASP.NET user.
I would like to speed this up by writing to a memory cache location. The problem is that threads in the custom thread pool can't call System.Web.HttpContext.Current (nor can they call System.Reflection.Assembly.GetEntryAssembly().GetName().Name) to find where they came from. I started to look into a shared memory sample, since the ASP.NET pool and custom thread pool are all inside aspnet_wp.exe "inside" the CLR, but it seems to be missing the example/sample projects (http://staff.develop.com/richardb/weblog/). Any thoughts greatly appreciated of course. =================================== This list is hosted by DevelopMentorŪ http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
