Ok. Uploaded new version now.<br><br><div class="gmail_quote">On Thu, Feb 4, 2010 at 10:30 AM, Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net">oej@edvina.net</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;">
<br>
3 feb 2010 kl. 21.41 skrev Håkon Nessjøen:<br>
<div><div></div><div class="h5"><br>
> On Wed, Feb 3, 2010 at 9:29 PM, Tilghman Lesher <<a href="mailto:tlesher@digium.com">tlesher@digium.com</a>> wrote:<br>
> 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>
> Tilghman<br>
><br>
><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>
</div></div>Ok, I buy Tilghman's arguments. Let's go with DEVICESTATE.<br>
<font color="#888888"><br>
/O<br>
</font><div><div></div><div class="h5">--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div><br>