I noticed that JsonDocument expects both all defined values to be set and
that those values to be in a specific order. This makes it impossible for
example to pass in a JSON string like '{ "idUri": "sip:192.168.100.10" }'
for reading into a TransportConfig object.
Is there currently any easy way to work around these issues?
- Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20140305/72bd8c41/attachment-0001.html>
