<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>I agree that this will reduce the effort required for new/infrequent users of the API – I recommend the change.</div>
<div>
<div>
<div>-- </div>
<div>Glen Wiley</div>
<div>KK4SFV</div>
</div>
<div>Sr. Engineer</div>
<div>The Hive, Verisign, Inc.</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><Goyal>, Neel <<a href="mailto:ngoyal@verisign.com">ngoyal@verisign.com</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, January 30, 2014 11:12 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:getdns-api@vpnc.org">getdns-api@vpnc.org</a>" <<a href="mailto:getdns-api@vpnc.org">getdns-api@vpnc.org</a>><br>
<span style="font-weight:bold">Subject: </span>[getdns-api] API review section 3.1.2 and 3.1.3<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font-family:Calibri,sans-serif">
<div>
<pre style="white-space:pre-wrap">This is commentary on the latter parts of section 3 in reference to Bob Steagall’s review of the getdns API - <a href="http://www.vpnc.org/pipermail/getdns-api/2014-January/000229.html">http://www.vpnc.org/pipermail/getdns-api/2014-January/000229.html</a></pre>
</div>
<div>Section 3.1.2 suggests appending _async to the existing functions where asynchronous behavior is used (I.e. getdns_get_general becomes getdns_get_general_async). I think this makes sense, given that we have _sync versions of these functions as well. Since
API users are typically used to synch behavior, having the function indicate that it is async may remind them and set expectations. Essentially, I agree with this proposal.</div>
<div><br>
</div>
<div>3.1.3 also makes sense to me - the verb should come first followed by the object beign operated on. This primarily affects the context methods (i.e. getdns_context_create => getdns_create_context, getdns_context_set_resolution_type => getdns_set_context_resolution_type).
Many code style guidelines follow this idiom.</div>
<div><br>
</div>
<div>Thoughts?</div>
<h5><font color="gray">“This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure
under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this
message in error, notify sender immediately and delete this message immediately.”
</font></h5>
<font color="gray"></font></div>
</div>
</span>
</body>
</html>