Well caching is the way to go., bu then again most of the current solutions have this problem.<br><br>John smit has a DID.. 514 555 1234 and closes account.. did sleeps for 3 months and new client Jane doe takes it..<br><br>
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.<br><br><br><br><br><div><span class="gmail_quote">
On 20 Feb 2007 20:43:37 +0100, <b class="gmail_sendername">Benny Amorsen</b> <<a href="mailto:benny+usenet@amorsen.dk">benny+usenet@amorsen.dk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
>>>>> "RL" == Richard Lyman <<a href="mailto:pchammer@dynx.net">pchammer@dynx.net</a>> writes:<br><br>RL> TP'n to follow flow just like DNS, the 'root servers' would still<br>
RL> see the high request hits, prior to passing off to local caching<br>RL> app.<br><br>The DNS root servers are almost only loaded by irrelevant traffic. The<br>root information is easily cacheable, so it is rare to have to
<br>actually ask the root servers.<br><br>An ENUM-style solution would most likely not see much garbage traffic,<br>and the relevant traffic is easily cacheable.<br><br>I doubt that we will ever see such a solution though; there is too
<br>much invested in the old way of doing things.<br><br><br>/Benny<br><br><br><br>_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --
<br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote>
</div><br><br clear="all"><br>-- <br>Mike<br>Sales Manager<br><a href="http://www.voicemeup.com">http://www.voicemeup.com</a><br>Making it happen<br>1.877.807.VOIP (8647)<br>1.514.312.7030