diff options
author | José Bollo <jose.bollo@iot.bzh> | 2016-07-27 15:16:11 +0200 |
---|---|---|
committer | José Bollo <jose.bollo@iot.bzh> | 2016-07-27 15:16:11 +0200 |
commit | 1d0f869ce3379089b4f4c5285e3d30e971e5b93d (patch) | |
tree | d1fb8f31da130b36b9135dcc9acdb979af052218 /doc/afb-bindings-writing.html | |
parent | 404f24c13cb45bd3e9ca837bc033fd6840cbf669 (diff) |
orthograph
Change-Id: I354649f885daf89426f3b1612127045fdf1dedcc
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
Diffstat (limited to 'doc/afb-bindings-writing.html')
-rw-r--r-- | doc/afb-bindings-writing.html | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/afb-bindings-writing.html b/doc/afb-bindings-writing.html index 20113a70..b32912b6 100644 --- a/doc/afb-bindings-writing.html +++ b/doc/afb-bindings-writing.html @@ -318,7 +318,7 @@ code > span.er { color: #ff0000; font-weight: bold; } <span class="co"> * Its send the object 'obj' (can be NULL) with an</span> <span class="co"> * informationnal comment 'info (can also be NULL).</span> <span class="co"> *</span> -<span class="co"> * For conveniency, the function calls 'json_object_put' for 'obj'.</span> +<span class="co"> * For convenience, the function calls 'json_object_put' for 'obj'.</span> <span class="co"> * Thus, in the case where 'obj' should remain available after</span> <span class="co"> * the function returns, the function 'json_object_get' shall be used.</span> <span class="co"> */</span> @@ -328,7 +328,7 @@ code > span.er { color: #ff0000; font-weight: bold; } <span class="co"> * Same as 'afb_req_success' but the 'info' is a formatting</span> <span class="co"> * string followed by arguments.</span> <span class="co"> *</span> -<span class="co"> * For conveniency, the function calls 'json_object_put' for 'obj'.</span> +<span class="co"> * For convenience, the function calls 'json_object_put' for 'obj'.</span> <span class="co"> * Thus, in the case where 'obj' should remain available after</span> <span class="co"> * the function returns, the function 'json_object_get' shall be used.</span> <span class="co"> */</span> @@ -343,7 +343,7 @@ code > span.er { color: #ff0000; font-weight: bold; } <span class="co"> * to call afb_req_success(NULL, info). Thus even if possible it</span> <span class="co"> * is strongly recommended to NEVER use "success" for status.</span> <span class="co"> *</span> -<span class="co"> * For conveniency, the function calls 'json_object_put' for 'obj'.</span> +<span class="co"> * For convenience, the function calls 'json_object_put' for 'obj'.</span> <span class="co"> * Thus, in the case where 'obj' should remain available after</span> <span class="co"> * the function returns, the function 'json_object_get' shall be used.</span> <span class="co"> */</span> @@ -353,13 +353,13 @@ code > span.er { color: #ff0000; font-weight: bold; } <span class="co"> * Same as 'afb_req_fail' but the 'info' is a formatting</span> <span class="co"> * string followed by arguments.</span> <span class="co"> *</span> -<span class="co"> * For conveniency, the function calls 'json_object_put' for 'obj'.</span> +<span class="co"> * For convenience, the function calls 'json_object_put' for 'obj'.</span> <span class="co"> * Thus, in the case where 'obj' should remain available after</span> <span class="co"> * the function returns, the function 'json_object_get' shall be used.</span> <span class="co"> */</span> <span class="dt">void</span> afb_req_fail_f(<span class="kw">struct</span> afb_req req, <span class="dt">const</span> <span class="dt">char</span> *status, <span class="dt">const</span> <span class="dt">char</span> *info, ...);</code></pre> <blockquote> -<p>For conveniency, these functions automatically call <strong>json_object_put</strong> to release <strong>obj</strong>. Because <strong>obj</strong> usage count is null after being passed to a reply function, it SHOULD not be used anymore. If exceptionally <strong>obj</strong> needs to remain usable after reply function then using <strong>json_object_get</strong> on <strong>obj</strong> to increase usage count and cancels the effect the <strong>json_object_put</strong> is possible.</p> +<p>For convenience, these functions automatically call <strong>json_object_put</strong> to release <strong>obj</strong>. Because <strong>obj</strong> usage count is null after being passed to a reply function, it SHOULD not be used anymore. If exceptionally <strong>obj</strong> needs to remain usable after reply function then using <strong>json_object_get</strong> on <strong>obj</strong> to increase usage count and cancels the effect the <strong>json_object_put</strong> is possible.</p> </blockquote> <h2 id="getting-argument-of-invocation">Getting argument of invocation</h2> <p>Many methods expect arguments. Afb-daemon's bindings retrieve arguments by name and not by position.</p> @@ -781,7 +781,7 @@ code > span.er { color: #ff0000; font-weight: bold; } <span class="co"> * 'object' can be NULL.</span> <span class="co"> * 'daemon' MUST be the daemon given in interface when activating the binding.</span> <span class="co"> *</span> -<span class="co"> * For conveniency, the function calls 'json_object_put' for 'object'.</span> +<span class="co"> * For convenience, the function calls 'json_object_put' for 'object'.</span> <span class="co"> * Thus, in the case where 'object' should remain available after</span> <span class="co"> * the function returns, the function 'json_object_get' shall be used.</span> <span class="co"> */</span> |