1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 2<html xml:lang="en-US" lang="en-US" xmlns="http://www.w3.org/1999/xhtml"> 3 <head> 4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 5 <meta http-equiv="Content-Style-Type" content="text/css" /> 6 <link rel="stylesheet" href="../../../css/manpage.css" type="text/css" /> 7<title>SetLazyPostDataSetting</title> 8 </head> 9 <body> 10<h1><CODE>nn::http::Connection::SetLazyPostDataSetting</CODE> Member Function</h1> 11<h2>Syntax</h2> 12 <div class="section"> 13 <pre class="definition"> 14<a href="../../../nn/Result/Overview.html">nn::Result</a> SetLazyPostDataSetting( 15 <a href="../../../nn/http/PostDataType.html">PostDataType</a> dataType 16); 17</pre> 18 </div> 19<h2>Arguments</h2> 20 <div class="section"> 21 <table class="arguments"> 22 <thead> 23 <tr> 24 <td width="15" /> 25<th>Name</th> 26<td>Description</td> 27 </tr> 28 </thead> 29 <tr> 30<td>in</td> 31<th>dataType</th> 32<td>Type of the POST data.</td> 33 </tr> </table> 34 </div> 35<h2>Return Values</h2> 36<div class="section">Returns the function's execution result. Returns a <CODE><a href="../../../nn/Result/Overview.html">Result</A></CODE> listed below. <br /> 37 <table class="arguments"> 38 <thead> 39 <tr> 40<th>Value</th> 41<td>Description</td> 42 </tr> 43 </thead> 44 <tr> 45<th><CODE>ResultSuccess</CODE></th> 46<td>Process was successful.</td> 47 </tr> 48 <tr> 49<th>ResultPostAddedAnotherErr</th> 50<td><CODE>POST</CODE> data has already been configured using the legacy configuration API for the <a href="../../../nn/http/Connection/Connect.html"><CODE>Connect</CODE></a> class. Use this function carefully to not conflict with such <CODE>POST</CODE> data configuration. (To reconfigure <CODE>POST</CODE> data, first call the <a href="../../../nn/http/Connection/Overview.html"><CODE>Connection</CODE></a> class's <a href="../../../nn/http/Connection/Finalize.html"><CODE>Finalize</CODE></a> function, and then call <a href="../../../nn/http/Connection/Initialize.html"><CODE>Initialize</CODE></a> again.)</td> 51 </tr> 52 <tr> 53<th>ResultConnectionStatusErr</th> 54<td>Error indicating an invalid state. This function cannot be called in the current communication state. (For example, the function returns this error if the system is already connected. You must call this function before calling <a href="../../../nn/http/Connection/Connect.html"><CODE>Connect</CODE></a>.)</td> 55 </tr> 56 <tr> 57<th>ResultNotConnectedErr</th> 58<td>Error indicating a <CODE>Connection</CODE> class instance for which the target URL is not assigned. The function has not done anything as it has been called on a <CODE>Connection</CODE> instance for which you have not yet successfully called <a href="../../../nn/http/Connection/Initialize.html"><CODE>Initialize</CODE></a>.</td> 59 </tr> 60 <tr> 61<th>ResultNotInitializedErr</th> 62<td>Error indicating that the library is not initialized. None of this library's functions can be used until you first call <a href="../../../nn/http/Initialize.html"><CODE>nn::http::Initialize</CODE></a>.</td> 63 </tr> 64 <tr> 65<th>A value other than the above.</th> 66<td>Unexpected error (See <CODE>http_Result.h</CODE> for details).</td> 67 </tr> 68 </table> </div> 69<h2>Description</h2> 70 <div class="section"> 71<p>Sets the "lazy" (delayed) POST data configuration mode. (Here, "lazy mode" refers to the mode used to specify data after <a href="../../../nn/http/Connection/Connect.html"><CODE>Connect</CODE></a> is called.) </p><p>Once this function is called, the lazy POST data configuration mode becomes possible. (With lazy mode, you can use one of the <CODE>SendPostData××</CODE> functions to set data after <a href="../../../nn/http/Connection/Connect.html"><CODE>Connect</CODE></a> or <a href="../../../nn/http/Connection/ConnectAsync.html"><CODE>ConnectAsync</CODE></a> is run.)<br /><br />When POST data is set to lazy mode, you can call one of the <CODE>SendPostData××</CODE> functions as many times as you like after calling either <a href="../../../nn/http/Connection/Connect.html"><CODE>Connect</CODE></a> or <a href="../../../nn/http/Connection/ConnectAsync.html"><CODE>ConnectAsync</CODE></a>.<br />The POST data is sent synchronously using one of the <CODE>SendPostData××()</CODE> functions. Consequently, <CODE>SendPostData××</CODE> will block until the send is complete.<br />Once you have finished configuring all of the POST data, you must run <a href="../../../nn/http/Connection/NotifyFinishSendPostData.html"><CODE>NotifyFinishSendPostData</CODE></a>. <br /><br />After running the <a href="../../../nn/http/Connection/NotifyFinishSendPostData.html"><CODE>NotifyFinishSendPostData</CODE></a> function, the library moves on to receiving the HTTP response.<br /></p><p><CODE>nn::http::POST_DATA_TYPE_URLENCODE:</CODE> If the data that was set is ASCII-encoded (in other words, if <a href="../../../nn/http/Connection/SendPostDataAscii.html"><CODE>SendPostDataAscii</CODE></a> was used to set it), the data is URL-encoded and then sent.<br />Either <a href="../../../nn/http/Connection/SendPostDataAscii.html"><CODE>SendPostDataAscii</CODE></a> or <a href="../../../nn/http/Connection/SendPostDataBinary.html"><CODE>SendPostDataBinary</CODE></a> can be used as the <CODE>SendPostData××</CODE> function. <br />If <a href="../../../nn/http/Connection/SendPostDataAscii.html"><CODE>SendPostDataAscii</CODE></a> was used, the data that is sent is URL-encoded data in which <CODE>[<labelName>=<data content>]</CODE>. <br />If <a href="../../../nn/http/Connection/SendPostDataBinary.html"><CODE>SendPostDataBinary</CODE></a> was used, the data that is sent is non-URL-encoded data in which <CODE>[<labelName>=<data content>]</CODE>. The labels and data that are set during a single call to <CODE>SendPostData××</CODE> are grouped into a single piece of chunked data and then sent.<br /><br /><br /><CODE>nn::http::POST_DATA_TYPE_MULTIPART</CODE>: The data that is set is sent as multipart MIME data.<br />Either <a href="../../../nn/http/Connection/SendPostDataAscii.html"><CODE>SendPostDataAscii</CODE></a> or <a href="../../../nn/http/Connection/SendPostDataBinary.html"><CODE>SendPostDataBinary</CODE></a> can be used as the <CODE>SendPostData××</CODE> function. The labels and data that are set during a single call to <CODE>SendPostData××</CODE> are prepended with <CODE>boundary</CODE> data and header fields, then grouped into a single piece of chunked data before being sent.<br />The label data that is configured is set as the <CODE>name</CODE> attribute of the <CODE>Content-Disposition</CODE> field.<br />(In other words, a header field of the form <CODE>"Content-Disposition:form-data; name=[Label]"</CODE> is added after the <CODE>boundary</CODE> data in the chunked data.)If any labels and data were configured using the <a href="../../../nn/http/Connection/SendPostDataBinary.html"><CODE>SendPostDataBinary</CODE></a> function, a <CODE>Content-Type</CODE> field is added after the <CODE>boundary</CODE> data of the chunked data.<br />(In this case, the field's content is <CODE>"Content-Type:application/octet-stream\r\nContent-Transfer-Encoding:binary\r\n"</CODE>. Data that was set using the <a href="../../../nn/http/Connection/SendPostDataAscii.html"><CODE>SendPostDataAscii</CODE></a> function does not have this field added to the chunked data.)<br /><br /><br /><CODE>nn::http::POST_DATA_TYPE_RAW</CODE>: Any data that is set is sent as is. Only <a href="../../../nn/http/Connection/SendPostDataRaw.html"><CODE>SendPostDataRaw</CODE></a> can be used as the <CODE>SendPostData××</CODE> function for this data type.<br />The data that is set during a single call to <a href="../../../nn/http/Connection/SendPostDataRaw.html"><CODE>SendPostDataRaw</CODE></a> are grouped into a single piece of chunked data and then sent.</p><!-- write here --></div> 72<h2>Revision History</h2> 73 <div class="section"> 74 <dl class="history"> 75 <dt>2010/06/14</dt> 76<dd>Initial version.<br /> 77 </dd> 78 </dl> 79 </div> 80 <hr><p>CONFIDENTIAL</p></body> 81</html>