Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code
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 RPC interfaces and fix them to be neat , sane and somewhat > consistent. > For example, there are still interfaces coding arrays as hashes with multiple > identically named fields (htable.dump is one i recently ran into) . There is > no > language and/or JSON/XML library i know of that can properly handle those > (most of them will just end up with the last entry). In such case the value can be constructed as an array. And I think leaving it at the free will means it won't happen -- we aimed at this since 2008 more or less. Hopefully there are only of few cases that need fixes and can be done while testing 5.0. But for htable there should not be more than one item with the same name, so such situation should not be for htable.dump. Can you give an example that you encountered, how do you set two items with same name? Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code
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 somewhat consistent. For example, there are still interfaces coding arrays as hashes with multiple identically named fields (htable.dump is one i recently ran into) . There is no language and/or JSON/XML library i know of that can properly handle those (most of them will just end up with the last entry). -- Alex Hermann ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code
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) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code
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 command does not > exist (or did not exist last time when I checked). > > Some years ago I tried to implement RPC version of pua_publish, but was > not able to get the call back working correctly. I also sent some > messages including a piece of code to the dev list, but it was a dead > end then. > > Very nice if pua.publish would see a day of light again. 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. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code
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 when I checked). Some years ago I tried to implement RPC version of pua_publish, but was not able to get the call back working correctly. I also sent some messages including a piece of code to the dev list, but it was a dead end then. Very nice if pua.publish would see a day of light again. -- Juha ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
