I know we have talked about rewriting app_queue for Asterisk 1.6, but once I
authorRussell Bryant <russell@russellbryant.com>
Mon, 21 May 2007 06:56:21 +0000 (06:56 +0000)
committerRussell Bryant <russell@russellbryant.com>
Mon, 21 May 2007 06:56:21 +0000 (06:56 +0000)
commitff73bfb7e708e48c93bd62117a5582861393819a
treeb0157454f3f78d70e42383ef9fa58a7734b1211e
parentde27bce777f5dadc1bbaca9f7c9f841835922c3d
I know we have talked about rewriting app_queue for Asterisk 1.6, but once I
saw this, I couldn't help myself from changing it.  Previously, for *every*
device state change, app_queue would spawn a thread to handle it.  Now, the
device state callback just puts the state change in a queue and it gets
handled by a single state change processing thread.

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@65298 65c4cc65-6c06-0410-ace0-fbb531ad65f3
apps/app_queue.c