Re: [reSIProcate] proposed accessors for SipMessage raw body
Hi Kennard,
What exactly is your use case? Handling a lot of 'unknown' content types?
I think it is a good idea to have a similar API to *RawHeader but I also like the ability to have customized objects to represent body types (you can dynamic_cast them, store custom data in them, have type safety, ...).
If your need is to handle unknown types, I wonder if using (or refactoring) GenericContents or PlainContents (or maybe creating an actual RawContents class) would work.
Regards,
Francis