> 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.
>

FYI - if you decide to go this route, you might look into using
ThreadPool.RegisterWaitForSingleObject; and let the CLR manage the thread &
waiting for you.

-Mike
http://www.bearcanyon.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

Reply via email to