On Fri, Jun 29, 2007 at 12:39:50AM +0900, bkml wrote: > > At present, the show command of the CLI will show objects in load > order (not alphabetical). I could replicate this behaviour in a > hashtable without any performance hit by augmenting the hashtable > with a doubly linked list structure for iteration.
Danger! Danger, Will Robinson! The module list is in load order so that reloads happen in the right order. How necessary that is I don't know but that's what an all too rare comment claims. > If we wanted the show command of the CLI to produce alphabetic order > while the CLI remains part of the server, then the server will take a > serious performance hit whenever the output has to be sorted. > > My thinking is that a hashtable augmented with a doubly linked list > structure for iteration (always returning the load order) is the way > to go. When the CLI is separated from the server, the CLI utility can > then be implemented so that it sorts the output alphabetically if > desired. This way, there will be no performance hit on the server. The job of the pbx is to handle calls. Design and optimize for that. If the CLI has to build its own list and sort it that's its problem. All the pbx needs to do is dump the needed data out without holding locks any longer than necessary. Mike -- Mike Jagdis Web: http://www.eris-associates.co.uk Eris Associates Limited Tel: +44 7780 608 368 Reading, England Fax: +44 118 926 6974 _______________________________________________ Callweaver-dev mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-dev
