Hi. I'm with LoudCity. We're a little over 1 year old, have two employees, and are a profitable company. You can read about us on loudcity.net and see one of our services in action on loudcity.com
We need help with a small project. It will require VB.NET and a solid understanding of multi-threaded applications and/or launching external processes and monitoring them.
We'll be building a hosted DJ service. Users are able to upload tracks to a storage location that we host. A DJ process shuffles the tracks and streams them to an audio server, we'll probably use Icecast for the audio server.
Most of the components are already built, or will be built by us.
We just need help coming up with a way to efficiently run a few hundred of these "DJ" processes on the same box.
We were thinking it could be done one of two ways:
- A windows application/service could spawn each "DJ" in a thread, and monitor each thread.
- A windows application/service could spawn each "DJ" as a separate process. Maybe in the form of a console application, and then monitor each process.
It's important to monitor each DJ so you can catch events, restart the DJ in the event of an error, and to issue general commands like Stop and Start.
If you have any of your own ideas, please share them.
If you are interested in this project, please contact us here.
We need help with a small project. It will require VB.NET and a solid understanding of multi-threaded applications and/or launching external processes and monitoring them.
We'll be building a hosted DJ service. Users are able to upload tracks to a storage location that we host. A DJ process shuffles the tracks and streams them to an audio server, we'll probably use Icecast for the audio server.
Most of the components are already built, or will be built by us.
We just need help coming up with a way to efficiently run a few hundred of these "DJ" processes on the same box.
We were thinking it could be done one of two ways:
- A windows application/service could spawn each "DJ" in a thread, and monitor each thread.
- A windows application/service could spawn each "DJ" as a separate process. Maybe in the form of a console application, and then monitor each process.
It's important to monitor each DJ so you can catch events, restart the DJ in the event of an error, and to issue general commands like Stop and Start.
If you have any of your own ideas, please share them.
If you are interested in this project, please contact us here.
