[asterisk-dev] Issue 16732 - device state change notification over manager
Olle E. Johansson
oej at edvina.net
Thu Feb 4 03:30:29 CST 2010
3 feb 2010 kl. 21.41 skrev Håkon Nessjøen:
> On Wed, Feb 3, 2010 at 9:29 PM, Tilghman Lesher <tlesher at digium.com> wrote:
> I'm fine with the general concept, but I think the name should be along the
> lines of DEVICESTATE or DEVICESTATUS. DEVICEINFO sounds a bit too generic and
> could potentially cause confusion with information about SIP peers and other
> types of information about specific devices.
>
> --
> Tilghman
>
>
> I thought to use the name DEVICESTATE would be too specific, since all the other classes are more general purpose ones. And since there wasn't a 'general' class for things like device states, I thought it could be nice to have DEVICEINFO for more generic events about devices that could be added to later.
>
> But if it is ok to have a specific class for the device state information, then I'm all in for using the name DEVICESTATE instead of DEVICEINFO.
>
Ok, I buy Tilghman's arguments. Let's go with DEVICESTATE.
/O
More information about the asterisk-dev
mailing list