On Tue, 11 Sep 2001, Christoph Reichenbach wrote: > On the other end, splitting up the sound server into process_message() and > process_sound() (as suggested) and calling it from a polling loop (which > could probably even be implemented generically, thanks to Pizza's > abstractions) for polling servers/calling them directly from event-based > systems seems like the way to go. This is what Sarien does in their gfx driver. It's called process_events(), I believe. If we need something to look at as a potential model, that should be it. -- http://www.clock.org/~matt
- [freesci-develop] Re: Event-driven sound server Stuffed Crust
- [freesci-develop] Re: Event-driven sound server Stuffed Crust
- [freesci-develop] Re: Event-driven sound server Stuffed Crust
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Matt
- [freesci-develop] Re: Event-driven sound server Alexander R Angas
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Stuffed Crust
- [freesci-develop] Re: Event-driven sound server Lars Skovlund
- [freesci-develop] Re: Event-driven sound server Matt
- [freesci-develop] Re: Event-driven sound server Matt
- [freesci-develop] Re: Event-driven sound server Stuffed Crust
- [freesci-develop] Re: Event-driven sound server Alexander R Angas
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Alexander R Angas
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
- [freesci-develop] Re: Event-driven sound server Alexander R Angas
- [freesci-develop] Re: Event-driven sound server Christoph Reichenbach
