Commits

Anonymous committed 810f4e1 Merge

merge

Comments (0)

Files changed (1)

 * {{{ wrq:stream_req_body/2 }}}
 * {{{ wrq:set_resp_body/2 }}}
 
-The first of these ({{{ wrq:req_body/1 }}}) is the simplest.  It will provide the whole incoming request body as a binary.  (Unless the body is too large, as set by {{{ wrq:set_max_recv_body/2 }}} or defaulting to 50M)  For the majority of resources, this is the easiest way to handle the incoming request body.
+The first of these ({{{req_body}}}) is the simplest.  It will provide the whole incoming request body as a binary.  (Unless the body is too large, as set by {{{ wrq:set_max_recv_body/2 }}} or defaulting to 50M)  For the majority of resources, this is the easiest way to handle the incoming request body.
 
-If a resource instead wants to handle the incoming request body a hunk at a time, it may call {{{ wrq:stream_req_body/2 }}} instead.  Instead of a binary, this produces a {{{ StreamBody }}} structure.
+If a resource wants to handle the incoming request body a hunk at a time, it may call {{{ wrq:stream_req_body/2 }}} instead.  Instead of a binary, this produces a {{{ StreamBody }}} structure.
 
 (It is an error to call both {{{ wrq:req_body/1 }}} and {{{ wrq:stream_req_body/2 }}} in the execution of a single resource.)