[Live-devel] rtsp client and server in the same app

[Mat Laibowitz]

The problem is the MPEG hardware. I can only have one open connection to
MPEG hardware for both encoding and decoding.
I don't need the client to talk to its local server. I need the client to
talk to a server on a remote device.
So if I have two devices one serves rtsp://ip1:8554/video and connects a
client to rtsp://ip2:8554/video in the same application and the other device
does the opposite.
I think this should be possible. I think they should bind to different
sockets and exists as different tasks in the scheduler.
It is failing at the readSocket command of the RTSP client's sendOptionsCmd
function.
Thanks,
-mat


On Sun, Oct 26, 2008 at 10:31 AM, Ross Finlayson <finlayson at live555.com>wrote:

> Yeah, but one is a server and one is a client, so it should work that way I
>> think.
>>
>
> Depending on your operating system, this might still not be possible.
>
> I suggest not doing what you are trying to do (run the client and the
> server that it's communicating with in the same application).  It's weird,
> and not useful (because the client and server are already communicating
> using sockets, rather than via shared memory, there's no need for them to
> reside within the same application).
> --
>
> 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/20081026/34dd29f0/attachment.html>