[Live-devel] SubClassing "OnDemandServerMediaSubsession"

[Robert Clove]

Hello Ross sir,

As stated in your reply i ran  multiple threads, each with their
own "UsageEnvironment" and "TaskScheduler".
It works fine.
But when i stop receiving the stream from the back-end server that is when
i call "deleteservermediasession" for that particular session and again
want to receive stream the backend server didnot stream.When i tried to
figure it out i saw that the port on which the back-end  server was
streaming is still showing the status of "ESTABLISHED" even after i have
called the "deleteservermediasession" for that particular session.
I really need your help.
I was searching the mailing list i found a ques in which the guy want to
stream multiple stream like one today and another day after tomorrow and
for them you have asked him to use " TaskScheduler::scheduleDelayedTask".
Can some thing like be used in our case?


Thanks



On Thu, Feb 14, 2013 at 8:47 PM, Ross Finlayson <finlayson at live555.com>wrote:

> First, DO NOT post the same question to the list multiple times.  This is
> a basic violation of 'netiquette' that everyone should know, and is
> explained clearly in the FAQ (that everyone is asked to read before posting
> to the mailing list).  You have (effectively) posted the same question to
> the list three times.  Because of this, all future postings from you (and
> anyone else from "interfaceinfosoft.com") will be moderated.
>
> My answer to the original question was very clear:
>
>
> The existing "LIVE 555 Proxy Server" can *already* stream concurrently
> from multiple back-end servers.  It does this as a single-threaded
> application (using an event loop, rather than threads, for concurrency)
>
>
>
>
>
> But the issue is that if am receiving one stream from backend rtsp server
> and then i want another stream to receive i call the proxy server media
> with new env and scheduler and without calling the do event loop again.
>
>
> As I explained before, you do not need to (and should not) do this.  You
> can receive from multiple streams using a *single* event loop, and thus a
> *single* "UsageEnvironment" and "TaskScheduler".  All operations (including
> your 'stop' operation) are performed by handling events from within the
> (single) event loop.
>
> As explained in the FAQ, you *can* run multiple threads, each with their
> own "UsageEnvironment" and "TaskScheduler".  However, if you do this, these
> threads must not interact (except perhaps via global variables).  So,
> that's probably not what you want.
>
>
> Ross Finlayson
> Live Networks, Inc.
> http://www.live555.com/
>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20130215/a631087c/attachment.html>