<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>MQX Software Solutions中的主题 Re: RTCS Connect</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/RTCS-Connect/m-p/269054#M8176</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Handy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The RTCS setsockopt() API permits the application to set the OPT_CONNECT_TIMEOUT option on a stream socket, which indicates the timeout (in millisec.) when a call to the connect API using that socket will return indicating a connection time-out error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The RTCS User's Guide appears to indicate the value specified for the OPT_CONNECT_TIMEOUT option is to be &amp;gt;= 180000 msec.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can change TCP_SENDTIMEOUT_MIN (tcp_prv.h) to your expected value &lt;/P&gt;&lt;P&gt;#define TCP_SENDTIMEOUT_MIN&amp;nbsp;&amp;nbsp; 100000L&amp;nbsp; /* as per RFC1122 4.2.3.5 */&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But it is not recommended, because it violates the RFC1122&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Daniel&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 03 Mar 2014 13:46:54 GMT</pubDate>
    <dc:creator>danielchen</dc:creator>
    <dc:date>2014-03-03T13:46:54Z</dc:date>
    <item>
      <title>RTCS Connect</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/RTCS-Connect/m-p/269053#M8175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to ask about the long timeout of RTCS Connect() function. I want to know is there any way for RTCS Connect() to return directly if it failed to connect ? Because i read that the function will return after timeout, and the minimum timeout for that is 3 mins.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Feb 2014 18:22:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/RTCS-Connect/m-p/269053#M8175</guid>
      <dc:creator>handychandra</dc:creator>
      <dc:date>2014-02-28T18:22:48Z</dc:date>
    </item>
    <item>
      <title>Re: RTCS Connect</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/RTCS-Connect/m-p/269054#M8176</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Handy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The RTCS setsockopt() API permits the application to set the OPT_CONNECT_TIMEOUT option on a stream socket, which indicates the timeout (in millisec.) when a call to the connect API using that socket will return indicating a connection time-out error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The RTCS User's Guide appears to indicate the value specified for the OPT_CONNECT_TIMEOUT option is to be &amp;gt;= 180000 msec.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can change TCP_SENDTIMEOUT_MIN (tcp_prv.h) to your expected value &lt;/P&gt;&lt;P&gt;#define TCP_SENDTIMEOUT_MIN&amp;nbsp;&amp;nbsp; 100000L&amp;nbsp; /* as per RFC1122 4.2.3.5 */&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But it is not recommended, because it violates the RFC1122&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Daniel&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Mar 2014 13:46:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/RTCS-Connect/m-p/269054#M8176</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2014-03-03T13:46:54Z</dc:date>
    </item>
    <item>
      <title>Re: RTCS Connect</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/RTCS-Connect/m-p/269055#M8177</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have another issue regarding to connect() in MQX 4.0 (seemed same in MQX 4.1) - the issue is:&lt;/P&gt;&lt;P&gt; - the connect timeout in 382 seconds - I did not use OPT_CONNECT_TIMEOUT in my code&lt;/P&gt;&lt;P&gt; - the TCP packet is sent, then received an ICMP destination unreachable message which is handled in ICMP_service() and then discarded - &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Why MQX did not sent to some routine in TCP family then send error back to wake up connect() function,&amp;nbsp; instead it keeps sending TCP SYN message in the sequences - 1s, 4s, 10s, 22s, 46s, 94s, 190s, 382s.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Is there a fix for this misbehavior? I am lost while trying to find a solution. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Sep 2014 20:34:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/RTCS-Connect/m-p/269055#M8177</guid>
      <dc:creator>David_Wu</dc:creator>
      <dc:date>2014-09-03T20:34:03Z</dc:date>
    </item>
  </channel>
</rss>

