<div class="gmail_quote">On Wed, Feb 3, 2010 at 9:29 PM, Tilghman Lesher <span dir="ltr"><<a href="mailto:tlesher@digium.com">tlesher@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm fine with the general concept, but I think the name should be along the<br>
lines of DEVICESTATE or DEVICESTATUS. DEVICEINFO sounds a bit too generic and<br>
could potentially cause confusion with information about SIP peers and other<br>
types of information about specific devices.<br>
<br>
--<br>
<font color="#888888">Tilghman<br>
</font><div><div></div><br></div></blockquote><div><br>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.<br>
<br>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.<br><br>--<br>Håkon<br></div></div>