[Asterisk-Users] CRM integration (was RE: CallerID)

Rusty Shackleford john97 at flatline.com
Wed May 25 14:01:56 MST 2005


> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com 
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of 
> Michiel van Baak
> Sent: Wednesday, May 25, 2005 12:04 PM
> To: asterisk-users at lists.digium.com
> Subject: Re: [Asterisk-Users] CRM integration (was RE: CallerID)
> > 
> > And that's the real trick. Web browsers, unless they are 
> instructed to 
> > do otherwise, don't DO anything once they've completed 
> loading a page. 
> > So without instructing them to refresh, they aren't going 
> to be aware 
> > of a server-side change, such as an incoming call. For that, you're 
> > going
> 
> This is not true. 

I beg to differ...
Please re-read my statement that "...unless instructed to do
otherwise..."

> If it was for pure HTML only, yes, you are 
> correct. But with javascript you can start a timer and 
> execute a javascript function every once in a while. If this 
> javascript loads an XML document off the server, you're there ;)

So you have now instructed the browser, via javascript, to periodically
poll the server "every once in a while".
This is exacly what the previous poster (the one I replied to) was
trying to AVOID, and for good reason. It doesn't scale. In order to be
effective as a way to present the user with caller-ID driven data, it
would have to poll quite frequently.  With a handful of clients
constantly doing this, the impact is inconsequential, but as the number
of clients hammering the server in this manner climbs, things are going
to break. 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 266.11.14 - Release Date: 05/20/2005
 




More information about the asterisk-users mailing list