From: "Scott Godin"
<slgodin@xxxxxxxxxxxx >
A
while back – it was suggested that we use an abstracted SdpContents
class in
the InviteSession code to allow app developers to plug in their own
SdpContents
classes.
I've been looking into creating a CSTA server with resip/dum – this
requires
that non-SDP contents are used in the offer/answer. What do people
think
about changing the InviteSession API's and callbacks to pass around
Contents
instead of SdpContents? And maybe a profile setting to indicate if the
InviteSession should walk through multipart bodies or not to find
SdpContents?
I would be strongly in favour - but then I'm
trying to do pretty much
the same thing. It seems to me that Contents would work just as well as
SdpContents in most places.
What I've done today is a nasty hack - I've derived my custom Contents
from
SdpContents, but completely overridden the inherited implementation.
This means
it can be passed in and out of all the relevant resiprocate functions,
but when
it is serialised / deserialised to the wire it looks the way I want it.
This
works, but I'm not particularly proud of it. It does demonstrate that
lots of
things work fine without meaningful SdpContents data. (I'm only using a
very simple
offer/answer scenario, which probably helps a lot.)
- Alan