Based on your reply, my understanding is that you are not currently using the structured format, but you would like to have it in the future in JSON format. Am I right?
-ovidiu On Wed, Mar 19, 2014 at 3:07 PM, Brett Nemeroff <br...@nemeroff.com> wrote: > I think the only reason for that is backwards compatibility with stuff > written for the other mi interfaces. > > > Honestly, my parsers for the MI output are ridiculous. It's really > complicated and prone to failure. I'd like to know if others share my > feeling here. > > For little things like "dr_reload" I don't really care. > > But for MI calls that return large amounts of user data, like dlg_list_ctx.. > Parsing it is kind of ridiculous... Anyone else share this feeling? > > I personally would love to see it structured in JSON format. :) > > -Brett > > > > On Wed, Mar 19, 2014 at 2:05 PM, Ovidiu Sas <o...@voipembedded.com> wrote: >> >> Hello Brett, >> >> It is true that the structured output mode was not implemented in the >> new module. >> It seems that having the output in one big chunk is the preferred >> method in the community. >> >> If there is a real demand for structured output, we can take a look into >> it. >> >> Regards, >> Ovidiu Sas >> >> >> On Wed, Mar 19, 2014 at 1:56 PM, Brett Nemeroff <br...@nemeroff.com> >> wrote: >> > I'd like to see the new module to be a drop in replacement for the old >> > one.. >> > >> > That being said... >> > >> > I was pretty surprised when I started down the path of the XMLRPC module >> > that the reply isn't structured. It was just one big object. >> > >> > I'd like a selectable option on the module so that it either operates: >> > 1. Legacy (one big output chunk) >> > 2. Structured, parable for each output node. >> > >> > Really if we are talking "deprecating" we need to support the old method >> > primarily or there will be a lot of broken code out there. >> > >> > -Brett >> > >> > >> > >> > On Wed, Mar 19, 2014 at 12:15 PM, Bogdan-Andrei Iancu >> > <bog...@opensips.org> >> > wrote: >> >> >> >> The whole idea is not to :) >> >> >> >> But more tests need to be done. >> >> >> >> Regards, >> >> >> >> Bogdan-Andrei Iancu >> >> OpenSIPS Founder and Developer >> >> http://www.opensips-solutions.com >> >> >> >> On 19.03.2014 17:39, Ali Pey wrote: >> >> >> >> Will this affect OpenSIPS-CP? >> >> >> >> Regards, >> >> Ali Pey >> >> >> >> >> >> >> >> On Wed, Mar 19, 2014 at 10:18 AM, Kneeoh <kne...@yahoo.com> wrote: >> >>> >> >>> I'm all for the deprecation as long as the documentation on the >> >>> mi_xmlrpc_ng module is updated to a usable level. I find myself >> >>> referencing >> >>> the documentation for xmlrpc and hoping that it holds true for >> >>> xmlrpc_ng. >> >>> >> >>> _______________________________________________ >> >>> Users mailing list >> >>> Users@lists.opensips.org >> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> Users mailing list >> >> Users@lists.opensips.org >> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> >> >> >> >> _______________________________________________ >> >> Users mailing list >> >> Users@lists.opensips.org >> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> > >> > >> > _______________________________________________ >> > Users mailing list >> > Users@lists.opensips.org >> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > >> >> >> >> -- >> VoIP Embedded, Inc. >> http://www.voipembedded.com >> >> _______________________________________________ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- VoIP Embedded, Inc. http://www.voipembedded.com _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
