Feature #529
don't use generated caps ever
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Tristan Matthews |
% Done: | 0% |
|
| Category: | milhouse | Spent time: | - | |
| Target version: | 0.7 | |||
| Resolution: | wontfix | Version: | ||
| Trac ticket ID: | 529 |
Description
Pros of using generated caps:
-A sender need not establish a tcp connection with a receiver.
Cons:
-No guarantee that a receiver's generated caps will match what a sender will send.
-Have to maintain make_caps.py script and anticipate every possible combination on the sender side. Additionally, this slows down compilation and is all around evil.
-Caps are MEANT to be communicated out of band for rtp (i.e. sip, sdp, etc.).
Solution:
get rid of make_caps.py and CapsParser, in addition get rid of --disable-caps-negotiation option.
History
Updated by Tristan Matthews about 3 years ago
need to start testing multicast before i can do this though.
Updated by Tristan Matthews about 3 years ago
- Status changed from New to In Progress
Updated by Tristan Matthews almost 3 years ago
Updated by Tristan Matthews almost 3 years ago
multicast working, pushing this back to 0.7 for interoperability.
Updated by Nicolas Bouillot about 1 year ago
- Status changed from In Progress to Closed
- Resolution set to wontfix