kbalt
sdp-types
Hi!
I just wanted to let you know that I'm maintaining a crate sdp-types which looks very similar to yours and we're using it as part of some components in GStreamer (e.g. for the new rtspsrc2 RTSP client implementation).
Is there anything specific missing from mine that you'd need, or any fundamental difference in the approach API-wise that I missed? Let me know if you'd be interested in migrating to sdp-types and if there's anything I could assist with!
Hey, I'd be open to migrate, but its currently missing a few things for me.
ezk-sdp-types generally encodes more of the information in types e.g. Connection (sdp-types) and Connection (ezk-sdp-types) Though I understand that in this case there's more than just IN for nettype and IP4/IP6 for addrtype so a string keeps the crate more flexible.
It also doesn't have a lot of support for attributes and leaves parsing/formatting to the user. ezk-sdp-types currently has types for a bunch of attributes I needed along the way.
For example:
extmapfingerprintfmtpgroupcandidatertcprtpmapcryptossrcsetupdirection
It'd be nice to keep the attribute parsing & formatting code in the sdp-types crates where it can be reused. This could be achieved by having a parse function on Attribute or adding a generic variant of Attribute::get_first_attribute_value.
I want to avoid having to essentially write similar code as this, when it could be provided by the types crate itself.
Yeah that's basically https://github.com/sdroege/sdp-types/issues/1 and something that was long on my todo list. I was hoping to move the code from rtspsrc2 back but didn't get to it yet :)
There's some initial work on this in https://github.com/sdroege/sdp-types/pull/25 . Can you check if that API would work for you, and if not what you'd prefer?