[OpenSIPS-Devel] New MI module names

[Vlad Patrascu]

Hi Dan,

Indeed, those module parameters will be renamed accordingly, it's still 
on the todo list.

As for the module names, they should now reflect the transport protocol 
and not the encoding, since the majority of modules use JSON. 'mi_html' 
and 'mi_xmlrpc_ng' are the only exceptions. Even though they are also 
over HTTP, it makes sense to differentiate them by encoding since they 
don't align with the internal MI interface(which is now JSON-RPC) and do 
a translation.

Regards,

Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com

On 03/22/2019 01:58 PM, Dan Pascu wrote:
> Another thing just occurred to me after I sent the message:
>
> I understand that mi_http was renamed to mi_html because it actually produces HTML output (over HTTP). Similarly, shouldn't mi_json have kept its name as it produces JSON (over HTTP)?
>
> On 22 Mar 2019, at 13:32, Dan Pascu wrote:
>
>> I see that mi_http was renamed to mi_html and mi_json to mi_http. However the module parameters kept their old names, which makes that mi_html has mi_http_* parameters and mi_http has parameters named mi_json_*
>>
>> Is this intentional or is the module rename still work in progress? As it stands it's very confusing.
>>
>> --
>> Dan
>>
>>
>>
>>
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>
> --
> Dan
>
>
>
>
>
> _______________________________________________
> Devel mailing list
> Devel at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel