i realized that with writing Custom values to astDB.
But i dont understand why we could not change existing state.
Is that a possibility of writing a state to memory and not the astDB or
multi-thread will cause severe damage?

On Jan 16, 2008 6:44 AM, Kevin P. Fleming <[EMAIL PROTECTED]> wrote:

> Clod Patry wrote:
>
> > After a quick discussion with Russell on IRC, he told me the answers is
> > pretty long why we can explicitly change a device state.
> >
> > So let's start a discussion around this :)
>
> There's no discussion to be had; you can't change the state of a real
> device, only virtual (custom ) devices. The device state of a *real*
> device will be managed by the module that provides that device (channel
> driver, parking, etc.).
>
> --
> Kevin P. Fleming
> Director of Software Technologies
> Digium, Inc. - "The Genuine Asterisk Experience" (TM)
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>



-- 
Clod Patry
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Reply via email to