Web Sockets for applications other than chat
I run a small call center where a small group of employees log into an authenticated ColdFusion web site. The purpose of the web site is to poll an Access database every 30 seconds, and any consumer asking for information (having submitted a lead from a web form that posts the customer info to the database) is then promptly contacted. At this point the process is conducted using an index page that refreshes (every 30 seconds via a meta refresh). But I am wondering if this is a scenario that would be better served through the use of web sockets?
I must say that web sockets is a new technology to myself. And upon my attempts to learn more via examples on the web, I find that the typical example consists of a web chat interface. That too is intriguing to myself, but I am most concerned with at this time with a means to better implement efficiencies to the index page. I estimate that 4,000 queries are made every day against the Access database. It works, but there must be a better way?
