Right thanks for the feedback.
We'll looking to making the changes to our subclasses.
Ross Finlayson wrote:
I've now released a new version (2009.02.13) that includes some, but
not all, of your suggested changes.
A synopsis of the changes are listed below.
1. Modified BasicUsageEnvironment0
I've now released a new version (2009.02.13) that includes some, but
not all, of your suggested changes.
A synopsis of the changes are listed below.
1. Modified BasicUsageEnvironment0::reportBackgroundError() to get
the errorResultMsgBuffer contents via a call to getResultMsg()
instead of a
Yes the RTP and RTCP ports could be obtained by parsing the SDP however
that's rather ugly and inefficient don't you think?
The new code is implemented in the OnDemandServerSubsession class. We
couldn't just subclass OnDemandServerSubsession as the information is
keep in the StreamState class wh
In answer to Matt Schuckmann:
I think that RTCP client port can be set from SDP description
(MediaSession).See RFC 3650.
For the server RTCP port I think that can be implemented in the object
OnDemandServerSubsession.
What do you think Ross?
__
Attached is a patch file for changes we've made to LIVE555 to support
functionality we needed for our application.
The patch is a diff of the 1/26/2009 release and our changes.
I hope this patch isn't to big and all of the changes make sense and
work with in your vision for the library.
If an
