[OpenSIPS-Users] [RFC] Deprecating mi_xmlrpc

[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 for one more release.

Best regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 14.03.2014 03:07, Ovidiu Sas wrote:
> 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.smith at gmail.com> wrote:
>> 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
>> xmlrpc, and the format for the content responses returned by the new
>> mi_xmlrpc_ng module is not the same as the old module (I don't remember the
>> details off the top of my head, but basically it was a difference being
>> double colon delimited and something else).
>>
>> It would really be beneficial if there was a way to control or configure the
>> format of the xml response to line up the same as the old formatting, so
>> that we could use it as a drop in replacement and not have to go rewrite a
>> hundred different alerts/scripts that rely upon mi_xmlrpc's current format.
>>
>>
>> On Fri, Mar 7, 2014 at 6:26 AM, Bogdan-Andrei Iancu <bogdan at opensips.org>
>> wrote:
>>> 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 old mi_xmlrpc module use the libxmlrpc-c3 external library for the
>>> HTTP server and XMLRPC engine. This library was a source of problems along
>>> the years because of the difficulty in using it (threads versus processes
>>> support) -> the user experience was horrible in trying to have this library
>>> properly working on various OS distros.
>>>
>>> The new mi_xmlrpc_ng module uses the httpd support from OpenSIPS and the
>>> generic libxml library - this is a safer and more robust approach ; users
>>> will find really easy to deploy these modules, to configure them (not to
>>> mention flexibility when comes to setting, restricting access, etc).
>>>
>>> So, I would suggest to terminate the mi_xmlrpc module and officially have
>>> the mi_xmlrpc_ng module for the XMLRPC backend.
>>>
>>> Comments, opinions are, as always, more than welcome.
>>>
>>> References :
>>>      - mi_xmlrpc module -
>>> http://www.opensips.org/html/docs/modules/1.10.x/mi_xmlrpc.html
>>>      - mi_xmlrpc_ng module -
>>> http://www.opensips.org/html/docs/modules/1.10.x/mi_xmlrpc_ng.html
>>>
>>> Regards,
>>>
>>> --
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developer
>>> http://www.opensips-solutions.com
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>