Blame the fever, but I've change my mind on a few points.
1) The vm<->soundsserver API does not need to change. This means I can
shoehorn my new soundserver into the fray alongside the others.
This is partially due to revelations in how SCI01+ explicitly polls
for updates, but mostly due to the "it's not necessary to gut
everything because the actual API is better than I thought and it's
only the implementations that suck."
2) I'm going to take the existing SDL Soundserver and transform it to
my new model. It won't break anything that wasn't already broken. :)
3) We need to finish song iterators ASAP. There are several things I
want to try out are practically begging for iterators. And besides,
they'll make all of the other soundservers much simpler.
That said, what's left to do with the song iterators? save/restore
only, right? If that's it, then I vote for immedately integrating 'em.
That'll motivate us to finish 'em relatively quickly!
- Pizza
--
Solomon Peachy pizza@f*cktheusers.org
I'm not broke, but I'm badly bent. ICQ #1318344
Patience comes to those who wait. Melbourne, FL
Quidquid latine dictum sit, altum viditur
-- Attached file included as plaintext by Listar --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9i6FrPuLgii2759ARAuh2AJ9pIDUX6xQqYaXFADL7eW2i6ZXHpQCfX5EP
9WbDJznO5+ySCCeqmGaGLPc=
=vVDL
-----END PGP SIGNATURE-----
