RJ: my initial thought was to spawn a thread to connect to shoutcast whenever a connection was needed but creating a separate thread for each sidechain feature would certainly be more extensible. I'm taking this up.
I have a hard time believing that our ~16 threads are of any consequence to modern process schedulers that happily handle hundreds of processes concurrently without issue.
RJ: my initial thought was to spawn a thread to connect to shoutcast whenever a connection was needed but creating a separate thread for each sidechain feature would certainly be more extensible. I'm taking this up.
I have a hard time believing that our ~16 threads are of any consequence to modern process schedulers that happily handle hundreds of processes concurrently without issue.