If there's no way to reduce the number of events (by sharing events) then you might have to just resort to using a timeout and polling or using a separate thread to wait on each block of 64 events and then get those threads to notify the main thread on one shared event.
> -----Original Message----- > From: Moderated discussion of advanced .NET topics. [mailto:ADVANCED- > [EMAIL PROTECTED] On Behalf Of Andrew Chalk > Sent: Sunday, 2 November 2003 3:06 p.m. > To: [EMAIL PROTECTED] > Subject: [ADVANCED-DOTNET] WaitHandle.WaitAny Limitations > > WaitHandle.WaitAny has a limitation of 64 events. Is there any way around > this limitation (for example, a systemwide parameter change or alternative > synchronization method)? > > Many thanks > > =================================== > This list is hosted by DevelopMentorR http://www.develop.com > Some .NET courses you may be interested in: > > Guerrilla ASP.NET, 10 Nov 2003 in London and 26 Jan 2004, in Los Angeles > http://www.develop.com/courses/gaspdotnet > > Guerrilla .NET, 8 Dec 2003, in Los Angeles > http://www.develop.com/courses/gdotnet > > View archives and manage your subscription(s) at > http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: Guerrilla ASP.NET, 10 Nov 2003 in London and 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnet Guerrilla .NET, 8 Dec 2003, in Los Angeles http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com
