Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Imagine a call center web application with a soft phone that automatically detects when a call has started or the caller has hung up. The obvious approach to receiving these messages would be some kind of server push (a.k.a. Comet). It's pretty disastrous if we miss one of those server pushes.

Must this application be written as a single-page JavaScript-heavy app, or is a more traditional multi-page app also a reliable option? (Or is this what iframes are for?)

My biggest worry about using a multi-page app is losing push messages when changing pages.

My biggest worry about using a single-page app is complexity.

share|improve this question

As far as I know, the soft dialler resides on a separate server by itself, and the agents interact using web interfaces. Your web app must introduce constraints on the agent like not being able to "change pages" without disposing a live call first. Now, If I were you, yes, I'd use "heavy" AJAX in my pages to accomplish this. Also, check out ViciDial if you're serious on writing your own CC suite.

I'd recommend a mix of AJAX and traditional multi-page setup (e.g., you don't need to AJAXify the log-out/log-in of an off-call agent)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.