Normal
Well this could be solved with a worker thread pool, so for each incoming client conexion, a own thread will be created starting to stream, but then no multicast(is this the correct word for it) is possible, so 1 client, 1 stream...But is there any scenario where you, in your home have multiple clients who require different positions in the timeshifting buffers?!new IDEA:why not making such a thread pool, and let the client decide if he wants to use this stream or wants to open another one?!
Well this could be solved with a worker thread pool, so for each incoming client conexion, a own thread will be created starting to stream, but then no multicast(is this the correct word for it) is possible, so 1 client, 1 stream...
But is there any scenario where you, in your home have multiple clients who require different positions in the timeshifting buffers?!
new IDEA:
why not making such a thread pool, and let the client decide if he wants to use this stream or wants to open another one?!
[/QUOTE]
