Hi list,
I was wondering if any work is in progress making dispatcher operate with non-numeric pool id's? Plans or todo's? Or may be some successor to replace dispatcher?
On 05 Apr 2016, at 12:39, Alekzander Spiridonov sipidronov@gmail.com wrote:
Hi list,
I was wondering if any work is in progress making dispatcher operate with non-numeric pool id's? Plans or todo's? Or may be some successor to replace dispatcher?
Not that I’m aware of.
Curious - what would be the benefit? Is there something you can’t easily do today that would work with non-numeric ID’s?
/O
No need to map whatever id is to a number. Let's say data is maintained by other sub-systems, so with current implementation either these sub-sys's have to work with digit id's only or K have to have some sort of mapping. Both options are not actually flexible.
Although I do understand that use of int id's was kind of an "over-optimization" =)
2016-04-05 16:06 GMT+03:00 Olle E. Johansson oej@edvina.net:
On 05 Apr 2016, at 12:39, Alekzander Spiridonov sipidronov@gmail.com
wrote:
Hi list,
I was wondering if any work is in progress making dispatcher operate
with non-numeric pool id's? Plans or todo's? Or may be some successor to replace dispatcher?
Not that I’m aware of.
Curious - what would be the benefit? Is there something you can’t easily do today that would work with non-numeric ID’s?
/O _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
On 05 Apr 2016, at 15:22, Alekzander Spiridonov sipidronov@gmail.com wrote:
No need to map whatever id is to a number. Let's say data is maintained by other sub-systems, so with current implementation either these sub-sys's have to work with digit id's only or K have to have some sort of mapping. Both options are not actually flexible.
Although I do understand that use of int id's was kind of an "over-optimization" =)
Well, at start we only had numeric route-names, but we changed that. Any source code to fix this in dispatcher would be welcome!
Cheers, /O
2016-04-05 16:06 GMT+03:00 Olle E. Johansson <oej@edvina.net mailto:oej@edvina.net>:
On 05 Apr 2016, at 12:39, Alekzander Spiridonov <sipidronov@gmail.com mailto:sipidronov@gmail.com> wrote:
Hi list,
I was wondering if any work is in progress making dispatcher operate with non-numeric pool id's? Plans or todo's? Or may be some successor to replace dispatcher?
Not that I’m aware of.
Curious - what would be the benefit? Is there something you can’t easily do today that would work with non-numeric ID’s?
/O _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org mailto:sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Best regards, Alekzander Spiridonov _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
As the first step I'd like to have some indexing to be used for ds_set lookup. Plz review implementation attached.
2016-04-05 16:58 GMT+03:00 Olle E. Johansson oej@edvina.net:
On 05 Apr 2016, at 15:22, Alekzander Spiridonov sipidronov@gmail.com wrote:
No need to map whatever id is to a number. Let's say data is maintained by other sub-systems, so with current implementation either these sub-sys's have to work with digit id's only or K have to have some sort of mapping. Both options are not actually flexible.
Although I do understand that use of int id's was kind of an "over-optimization" =)
Well, at start we only had numeric route-names, but we changed that. Any source code to fix this in dispatcher would be welcome!
Cheers, /O
2016-04-05 16:06 GMT+03:00 Olle E. Johansson oej@edvina.net:
On 05 Apr 2016, at 12:39, Alekzander Spiridonov sipidronov@gmail.com
wrote:
Hi list,
I was wondering if any work is in progress making dispatcher operate
with non-numeric pool id's? Plans or todo's? Or may be some successor to replace dispatcher?
Not that I’m aware of.
Curious - what would be the benefit? Is there something you can’t easily do today that would work with non-numeric ID’s?
/O _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Best regards, Alekzander Spiridonov _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hello,
thanks for the patch. Can you make a pull request on github kamailio project? - https://github.com/kamailio/kamailio
It will be easier to review and CI tools will compile it once other changes are done and reveal if it gets broken.
Cheers, Daniel
On 20/04/16 15:03, Alekzander Spiridonov wrote:
As the first step I'd like to have some indexing to be used for ds_set lookup. Plz review implementation attached.
2016-04-05 16:58 GMT+03:00 Olle E. Johansson <oej@edvina.net mailto:oej@edvina.net>:
On 05 Apr 2016, at 15:22, Alekzander Spiridonov <sipidronov@gmail.com <mailto:sipidronov@gmail.com>> wrote: No need to map whatever id is to a number. Let's say data is maintained by other sub-systems, so with current implementation either these sub-sys's have to work with digit id's only or K have to have some sort of mapping. Both options are not actually flexible. Although I do understand that use of int id's was kind of an "over-optimization" =)Well, at start we only had numeric route-names, but we changed that. Any source code to fix this in dispatcher would be welcome! Cheers, /O2016-04-05 16:06 GMT+03:00 Olle E. Johansson <oej@edvina.net <mailto:oej@edvina.net>>: > On 05 Apr 2016, at 12:39, Alekzander Spiridonov <sipidronov@gmail.com <mailto:sipidronov@gmail.com>> wrote: > > Hi list, > > I was wondering if any work is in progress making dispatcher operate with non-numeric pool id's? Plans or todo's? Or may be some successor to replace dispatcher? Not that I’m aware of. Curious - what would be the benefit? Is there something you can’t easily do today that would work with non-numeric ID’s? /O _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org <mailto:sr-dev@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev -- Best regards, Alekzander Spiridonov _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org <mailto:sr-dev@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev_______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org <mailto:sr-dev@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev-- Best regards, Alekzander Spiridonov
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Sure, will do. Thank you.
2016-04-21 9:33 GMT+03:00 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
thanks for the patch. Can you make a pull request on github kamailio project?
It will be easier to review and CI tools will compile it once other changes are done and reveal if it gets broken.
Cheers, Daniel
On 20/04/16 15:03, Alekzander Spiridonov wrote:
As the first step I'd like to have some indexing to be used for ds_set lookup. Plz review implementation attached.
2016-04-05 16:58 GMT+03:00 Olle E. Johansson oej@edvina.net:
On 05 Apr 2016, at 15:22, Alekzander Spiridonov sipidronov@gmail.com wrote:
No need to map whatever id is to a number. Let's say data is maintained by other sub-systems, so with current implementation either these sub-sys's have to work with digit id's only or K have to have some sort of mapping. Both options are not actually flexible.
Although I do understand that use of int id's was kind of an "over-optimization" =)
Well, at start we only had numeric route-names, but we changed that. Any source code to fix this in dispatcher would be welcome!
Cheers, /O
2016-04-05 16:06 GMT+03:00 Olle E. Johansson < oej@edvina.net oej@edvina.net>:
On 05 Apr 2016, at 12:39, Alekzander Spiridonov sipidronov@gmail.com
wrote:
Hi list,
I was wondering if any work is in progress making dispatcher operate
with non-numeric pool id's? Plans or todo's? Or may be some successor to replace dispatcher?
Not that I’m aware of.
Curious - what would be the benefit? Is there something you can’t easily do today that would work with non-numeric ID’s?
/O _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Best regards, Alekzander Spiridonov _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Best regards, Alekzander Spiridonov
sr-dev mailing listsr-dev@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Daniel-Constantin Mierlahttp://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com
-
Alekzander Spiridonov -
Daniel-Constantin Mierla -
Olle E. Johansson