Reply to thread

Message

<blockquote data-quote="samuel337" data-source="post: 42276" data-attributes="member: 10347">Um... I don't know how you interpreted it, but all I meant was looking at the other systems and see how they implemented this, then maybe take that idea and build on it if needed.Thread-pooling - good idea, build I think it needs to a bit more transparent. I don't think the user should have to deal with selecting a certain stream etc. Besides, sometimes its better if one person doesn't know what the other users are watching. Maybe, let's say user 1 is watching channel 1 live on a client. Now, user 2 comes along on another screen and decides to watch channel 1 live too. Suddenly, the phone rings and user 2 needs to pause the stream. The client should automatically start another thread on the server and connect itself to it, then pause it.So now, user 1 and user 2 are watching individual threads, but the whole process is transparent.Sam</blockquote>

[QUOTE="samuel337, post: 42276, member: 10347"] Um... I don't know how you interpreted it, but all I meant was looking at the other systems and see how they implemented this, then maybe take that idea and build on it if needed. Thread-pooling - good idea, build I think it needs to a bit more transparent. I don't think the user should have to deal with selecting a certain stream etc. Besides, sometimes its better if one person doesn't know what the other users are watching. Maybe, let's say user 1 is watching channel 1 live on a client. Now, user 2 comes along on another screen and decides to watch channel 1 live too. Suddenly, the phone rings and user 2 needs to pause the stream. The client should automatically start another thread on the server and connect itself to it, then pause it. So now, user 1 and user 2 are watching individual threads, but the whole process is transparent. Sam [/QUOTE]

Verification