Well caching is the way to go., bu then again most of the current solutions have this problem.
John smit has a DID.. 514 555 1234 and closes account.. did sleeps for 3 months and new client Jane doe takes it.. Now how long should caching be ? this is a big problem ATM because some cache for 1 year others 1 day , they don't want to tell how long nor provider an API update method. On 20 Feb 2007 20:43:37 +0100, Benny Amorsen <[EMAIL PROTECTED]> wrote:
>>>>> "RL" == Richard Lyman <[EMAIL PROTECTED]> writes: RL> TP'n to follow flow just like DNS, the 'root servers' would still RL> see the high request hits, prior to passing off to local caching RL> app. The DNS root servers are almost only loaded by irrelevant traffic. The root information is easily cacheable, so it is rare to have to actually ask the root servers. An ENUM-style solution would most likely not see much garbage traffic, and the relevant traffic is easily cacheable. I doubt that we will ever see such a solution though; there is too much invested in the old way of doing things. /Benny _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
-- Mike Sales Manager http://www.voicemeup.com Making it happen 1.877.807.VOIP (8647) 1.514.312.7030
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
