<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 01/24/2012 04:59 PM, Bryant Zimmerman wrote:
<blockquote cite="mid:7da65982$37bce131$46c94566$@com" type="cite"><span
style="font-family: Arial,Helvetica,sans-serif; font-size:
10pt;">Danny Nicholas pointed out to me the info below about the
concise option be deprecated. My question is if it is going to
pulled long term why is the verbose option truncating the
information. They both have a different purpose the verbose
option is not useful as it does not return the full data. This
would kill all of our outside channel monitoring code that uses
the asterisk -rx "core show channels concise". What is
the thinking behind this move. <br>
<div>
<p class="MsoNormal"><span style="font-family:
'calibri','sans-serif'; color: rgb(31, 73, 125);
font-size: 11pt;">From cli.c (asterisk 10)<br>
</span><span style="font-family: 'calibri','sans-serif';
color: rgb(31, 73, 125); font-size: 11pt;">
e->command = "core show channels
[concise|verbose|count]";<br>
</span><span style="font-family: 'calibri','sans-serif';
color: rgb(31, 73, 125); font-size: 11pt;">
e->usage =<br>
</span><span style="font-family: 'calibri','sans-serif';
color: rgb(31, 73, 125); font-size: 11pt;">
"Usage: core show channels [concise|verbose|count]\n"<br>
</span><span style="font-family: 'calibri','sans-serif';
color: rgb(31, 73, 125); font-size: 11pt;">
" Lists currently defined channels and some
information about them. If\n"<br>
</span><span style="font-family: 'calibri','sans-serif';
color: rgb(31, 73, 125); font-size: 11pt;">
" 'concise' is specified, the format is abridged and
in a more easily\n"<br>
</span><span style="font-family: 'calibri','sans-serif';
color: rgb(31, 73, 125); font-size: 11pt;"> "
machine parsable format. If 'verbose' is specified, the
output includes\n"<br>
</span><span style="font-family: 'calibri','sans-serif';
color: rgb(31, 73, 125); font-size: 11pt;">
" more and longer fields. If 'count' is specified
only the channel and call\n"<br>
</span><span style="font-family: 'calibri','sans-serif';
color: rgb(31, 73, 125); font-size: 11pt;">
" count is output.\n"<br>
</span><span style="font-family: 'calibri','sans-serif';
color: rgb(31, 73, 125); font-size: 11pt;">
" The 'concise' option is deprecated and will be
removed from future versions\n"<br>
</span><span style="font-family: 'calibri','sans-serif';
color: rgb(31, 73, 125); font-size: 11pt;">
" of Asterisk.\n";<br>
</span><span style="font-family: 'calibri','sans-serif';
color: rgb(31, 73, 125); font-size: 11pt;">
return NULL;<br>
</span><br>
Thanks<br>
<br>
Bryant<br>
</p>
</div>
</span></blockquote>
<tt>The thinking is that CLI commands are intended for human
consumption, not for parsing by code. This frees us to be able to
make changes to CLI commands when they have typos, are formatted
badly, or are missing information without the worry that it will
mess up somebody's parsing code.<br>
<br>
The "core show channels verbose" command was written before this
thinking came into play. The preferred method for handling this
sort of task is via the Asterisk Manager Interface's
CoreShowChannels command instead.<br>
<br>
One thing that also should be mentioned is that we also operate
under the philosophy (since about 1.6.0 or thereabouts) that even
when something becomes deprecated, we won't remove it. People like
to have stress-free upgrades if at all possible, and so if it
doesn't actually hurt to leave the code in, then we'll leave it
in. However, don't expect quick turnaround if you report a bug in
something that is declared deprecated, and don't expect any
updates to happen to deprecated code either.<br>
<br>
Mark Michelson<br>
</tt>
</body>
</html>