Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-10-07 Thread Bogdan-Andrei Iancu
Hi Ovidiu, We need to check once again if the mi_xmlrpc_ng can do a perfect replace for mi_xmlrpc - then we can obsolete in a blink of an eye. Are you aware of any pending issues in terms of backward compatibility ? PS: 1.12 is replaced by 2.1.0 - this is the version on trunk. Regards,

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-10-07 Thread Bogdan-Andrei Iancu
The trunk (development code) was switched from 1.12.x to 2.1.x and you can get the URL from http://www.opensips.org/Downloads/Downloads#toc4. The trunk version is not for production. See the available versions here: http://www.opensips.org/About/AvailableVersions Regards, Bogdan-Andrei Iancu

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-10-07 Thread Ovidiu Sas
There was a lot of work done right before releasing 1.11 to fix the compatibility issue. I didn't heard back anything, so I assume that it's fixed. Anyway, if there's no push for it, the transition will never happen :) -ovidiu On Oct 7, 2014 5:24 AM, Bogdan-Andrei Iancu bog...@opensips.org

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-10-07 Thread Bogdan-Andrei Iancu
Ovidiu, we are still somewhere in the middle of a release cycle, so enough time to eventually fix potential problems. I agree with you, we need to take the step and face the outcome. We need to prepare a directly on the repo, like modules_old where to move the obsolete modules. Regards,

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-09-26 Thread Satish Patel
Where is the trunk git URL to download latest 1.12.x? does it ready for production? On Thu, Sep 25, 2014 at 2:39 PM, Ovidiu Sas o...@voipembedded.com wrote: Are we ready to deprecate the mi_xmlrpc module now (for 1.12)? -ovidiu On Fri, Mar 21, 2014 at 11:24 AM, Bogdan-Andrei Iancu

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-09-25 Thread Ovidiu Sas
Are we ready to deprecate the mi_xmlrpc module now (for 1.12)? -ovidiu On Fri, Mar 21, 2014 at 11:24 AM, Bogdan-Andrei Iancu bog...@opensips.org wrote: Hello all, Bringing some light here : none of the xmlrpc implementations offer a structured reply From the deprecation point of view, we

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-21 Thread Bogdan-Andrei Iancu
Hello all, Bringing some light here : none of the xmlrpc implementations offer a structured reply From the deprecation point of view, we need to be sure: 1) the new mi_xmlrpc-ng module is a perfect substitute to the old one (providing the same unstructured reply) 2) the new mi_xmlrpc-ng

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Bogdan-Andrei Iancu
Hi, What Bobby state is really true - already had some chat with Ovidiu in evaluating the differences (on the reply format) and the effort to align the new xmlrpc-ng module with the old one. If this will be doable by tomorrow, we will drop mi_xmlrpc module in 1.11. If not, it will be kept

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Dragomir Haralambiev
Hello, The new mi_xmlrpc_ng module have one big probelm - not support integer value. To send digit value OpenSips want to use srting. Example: When try to change debug level I must ot send debug 1. workable XML this is : methodCall methodNamedebug/methodName params param

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Kneeoh
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

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Bogdan-Andrei Iancu
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

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Brett Nemeroff
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

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Ovidiu Sas
Please pull from git, give it a try and let us know if everything is working as expected with your old scripts. Regards, Ovidiu Sas On Tue, Mar 11, 2014 at 9:48 PM, Bobby Smith bobby.sm...@gmail.com wrote: The one thing we find annoying about deprecating this is that it's not a drop in

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Ovidiu Sas
Please let us know what's missing from the mi_xmlrpc_ng doc and it is present in mi_xmlrpc doc. Regards, Ovidiu Sas 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

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Ovidiu Sas
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,

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Brett Nemeroff
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

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Ovidiu Sas
Hello Dragomir, As I pointed to you in a previous e-mail, the integer is not really supported by opensips. Even if you send a value as integer, it will still be treated as string and each module will decide if a conversion is required. All you need to do is adjust your script to send out string

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Ovidiu Sas
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

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Brett Nemeroff
I presently use either the raw fifo, the UDP fifo or the old XMLRPC method. They all return the same format which has double colon separated nodes. It's not easy to parse into an object by any language I know. I've written parsers for it, but I don't like them. It seems like the structure isn't

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Dragomir Haralambiev
I totally share Brett's feelings! For me dlg_list_ctx over the new module causes lots of headaches when dialogs go over 100 or so. Structured output would resolve such problems. I am totally in for structured SJON format too! 2014-03-19 21:07 GMT+02:00 Brett Nemeroff br...@nemeroff.com: I

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Brett Nemeroff
I think there are some other issues with the size of the return data. I know for one that the mi_udp method has a buffer size limit. If you hit this limit I think it very quietly truncates the data. I can't 100% verify that since it's been a long time since I've used it. I believe you can

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Ovidiu Sas
So, you are using the raw format. The mi_xmlrpc_ng module is using only the raw format. The structured format in the old mi_xmlrpc module was not implemented in the new module because it seems that it doesn't have enough traction in the community (AFAIK). As for returning JSON, that should be a

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Ovidiu Sas
The new module is built on top of the httpd module which has a parameter to define the size of the buffer. If you need large replies, then you need to adjust the buffer size accordingly. http://www.opensips.org/html/docs/modules/devel/httpd That buffer is used by all modules that are sitting on

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-19 Thread Brett Nemeroff
JSON+http sounds fantastic. It's like.. Starting to sound a like a RESTful server. I'm pretty sure others will jump on this. I know I would. -Brett On Wed, Mar 19, 2014 at 2:52 PM, Ovidiu Sas o...@voipembedded.com wrote: The new module is built on top of the httpd module which has a

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-13 Thread Ovidiu Sas
Please open a bug report with all the details. We will take a look at it and see what can be done before the release. Regards, Ovidiu Sas On Tue, Mar 11, 2014 at 9:48 PM, Bobby Smith bobby.sm...@gmail.com wrote: The one thing we find annoying about deprecating this is that it's not a drop in

Re: [OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-11 Thread Bobby Smith
The one thing we find annoying about deprecating this is that it's not a drop in replacement for the current xmlrpc implementation. We have a lot of system level monitoring an alerting (things like fraud checking, rate limiting, reporting to external systems) that rely upon accessing fifo via

[OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

2014-03-07 Thread Bogdan-Andrei Iancu
Hello all, I would appreciate your input/opinions in the matter of deprecating the mi_xmlrpc module in favor of mi_xmlrpc_ng + httpd modules. Both modules offer the same functionality : XMLRPC backend for the Management Interface (see ww.opensips.org/Documentation/Interface-MI-1-10). The