Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code

2016-12-02 Thread Daniel-Constantin Mierla
On 02/12/2016 11:21, Alex Hermann wrote: > On donderdag 1 december 2016 15:17:18 CET Daniel-Constantin Mierla wrote: >> RPC is the alternative, a more standardized >> concept, with better structured format. > Before removing MI and letting everyone move to RPC, it might be wise to go > over all

Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code

2016-12-02 Thread Alex Hermann
On donderdag 1 december 2016 15:17:18 CET Daniel-Constantin Mierla wrote: > RPC is the alternative, a more standardized > concept, with better structured format. Before removing MI and letting everyone move to RPC, it might be wise to go over all RPC interfaces and fix them to be neat , sane and

Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code

2016-12-02 Thread Juha Heinanen
Daniel-Constantin Mierla writes: > Can you find that discussion in the archive? Open an item on bug tracker > and add the link to the discussion there, so we don't forget about it. Done, Juha ___ SIP Express Router (SER) and Kamailio (OpenSER) -

Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code

2016-12-02 Thread Daniel-Constantin Mierla
On 02/12/2016 00:24, Juha Heinanen wrote: > Brandon Armstead writes: > >> +1 - I'm all for cleaning up any technical debt and moving on with more >> normalized concept. > I'm also in favor of getting rid on MI interface. I'm myself relying > only on one MI command (pua_publish) for which an RPC

Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code

2016-12-01 Thread Juha Heinanen
Brandon Armstead writes: > +1 - I'm all for cleaning up any technical debt and moving on with more > normalized concept. I'm also in favor of getting rid on MI interface. I'm myself relying only on one MI command (pua_publish) for which an RPC command does not exist (or did not exist last time