[freesci-develop] Re: Event-driven sound server

[Christoph Reichenbach]

Hi,

(oops, forgot this part of the mail):

> When it comes down to it, the differences between the various
> soundservers are as follows:
> 
> 1) how it's started (ie fork(), new thread, etc)
> 2) how the game loop signals the sound server
> 3) how the soundserver passes cues back to the game
> 4) the mechanism we use to sleep until the next note is fired.

OK. This is all fine on UNIX, Win32, VMS, DOS, and other systems where
this is possible.
However, PalmOS and MacOS classic provide MIDI output as an OS service-
OTOH, they do _not_ provide v?fork() or MT (AFAIK).

Now I'm aware that we're pretty far from supporting these anyway-
FreeSCI's nowhere near the portability Sarien has achieved- but at least
MacOS classic might be a worthwhile port, and we should at least consider
its perceived deficiencies when designing a new sound architecture.

llap,
 Christoph