> On 05 Apr 2016, at 15:22, Alekzander Spiridonov <[email protected]> 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 <[email protected] 
> <mailto:[email protected]>>:
> 
> > On 05 Apr 2016, at 12:39, Alekzander Spiridonov <[email protected] 
> > <mailto:[email protected]>> 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
> [email protected] <mailto:[email protected]>
> 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
> [email protected]
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

Reply via email to