Oops - I said the other day that this release would be getting rid
of the "RTPOverTCP_OK" hack altogether. I forgot to do this.
However, I'm going to remove it from an upcoming release - so you
should just ignore it.
Ross, I'm confused--when you say you're removing that hack all
together, d
On Sun, Mar 14, 2010 at 6:36 PM, Ross Finlayson wrote:
> Does this release also address the RTPOverTCP_OK variable?
>>
>
> Oops - I said the other day that this release would be getting rid of the
> "RTPOverTCP_OK" hack altogether. I forgot to do this. However, I'm going
> to remove it from an u
Does this release also address the RTPOverTCP_OK variable?
Oops - I said the other day that this release would be getting rid of
the "RTPOverTCP_OK" hack altogether. I forgot to do this. However,
I'm going to remove it from an upcoming release - so you should just
ignore it.
--
Ross Finla
Does this release also address the RTPOverTCP_OK variable?
-Jeremy
>
>
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
Can we now remove the "hack" you put in for version "2009.11.27"
that removed the GET_PARAMETER option being listed as valid after an
OPTIONS command is received? I believe the fix you put in place
will now allow clients to call GET_PARAMETER if they wish.
Yes, that hack can now be removed.
Thanks Ross,
Can we now remove the ³hack² you put in for version ³2009.11.27² that
removed the GET_PARAMETER option being listed as valid after an OPTIONS
command is received? I believe the fix you put in place will now allow
clients to call GET_PARAMETER if they wish.
(RTSPServer.cpp:452)
Rega
