[Asterisk-Dev] IAX friend building perf

[Preston Garrison]

No i talked to kram about it, sounded like he didn't want it 
implemented so i didn't bother.

Preston Garrison
direct: 877-748-4142
fax: 310-774-3901
cell: 623-748-4140

-----Original Message-----
From: Michael Giagnocavo <mgg-digium at atrevido.net>
To: 'Asterisk Developers Mailing List' <asterisk-dev at lists.digium.com>
Sent: Tue, 15 Mar 2005 15:02:48 -0600
Subject: RE: [Asterisk-Dev] IAX friend building perf

Do you have a patch submitted anywhere? :)

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Preston 
Garrison
Sent: Tuesday, March 15, 2005 2:51 PM
To: asterisk-dev at lists.digium.com
Subject: Re: [Asterisk-Dev] IAX friend building perf

few lines in sip_Chan.c, few lines in chan_iax.c and one line in a main
asterisk file would make it so all would be allowed to implement their
own modules to build sip peers, sip users, etc directly.  Which would
elivate the problem for everyone.   I store everything on my servers in
binary format, with hash looks, and in memory hash tables.  My
switching performance is somewhere close to the most expensive phone
and network switches.

Preston Garrison
direct: 877-748-4142
fax: 310-774-3901
cell: 623-748-4140

-----Original Message-----
From: Kevin P. Fleming <kpfleming at starnetworks.us>
To: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
Sent: Tue, 15 Mar 2005 13:29:57 -0700
Subject: Re: [Asterisk-Dev] IAX friend building perf

Michael Giagnocavo wrote:
  > Hashtables are the answer? That's the "correct" way to avoid this
silly
   > O(N*N) thing. But, talking in #asterisk, someone made it quite 
clear
that
  > hashtables were not going to be allowed in because someone "likes
linked
 > lists".

 That depends on what part of the code you are talking about.

  Using hashtables for storage of peers/users/friends/channels/etc. is
on its way.

  Using hashtables for storage of config file contents so that they can
be parsed is not likely to happen, for the simple reason that Asterisk
config files allow the same variable to be specified more than one
time, and the order of appearance _must_ be preserved. Hashtables
cannot do that.

  However, I do have some other stuff in the works that will help this
problem to some degree, but it's quite a ways to go before it will
usable and even ready to be posted.
 _______________________________________________
 Asterisk-Dev mailing list
 Asterisk-Dev at lists.digium.com
 http://lists.digium.com/mailman/listinfo/asterisk-dev
 To UNSUBSCRIBE or update options visit:
 http://lists.digium.com/mailman/listinfo/asterisk-dev

_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev


_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev