JSON serializer/deserializer strictness

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Mar 6, 2014 at 4:41 AM, Brian White <mscdex at mscdex.net> wrote:

> 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?
>
>
>
Probably no. Why do want it like that though?

Best regards,
 Benny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20140306/e16e4cce/attachment-0001.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux