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 Developerhttp://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 > listUsers@lists.opensips.orghttp://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
