<?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>ColdFire/68K Microcontrollers and ProcessorsのトピックWhich HTTPd is better for M5225X?</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Which-HTTPd-is-better-for-M5225X/m-p/177550#M7057</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to complete the existing demo http web servers with necessary features: HTTP basic authentication, POST method and DHCP client. I evaluated MQX demo project, Niche + CMX demo, digibutler projects, FreeRTOS demo, uC/OS-II demo. According to my test result, the MQX demo has the most stable performance. So I hope to use MQX demo as code base, although Digibutler has implemented the authentication part. And I saw the authentication code is implemented in RTCS/MQX. However, the RTCS pdf in MQX is very comprehensive, but not too much on http server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know how to use the RTCS HTTP?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 02 May 2009 20:00:22 GMT</pubDate>
    <dc:creator>allankliu</dc:creator>
    <dc:date>2009-05-02T20:00:22Z</dc:date>
    <item>
      <title>Which HTTPd is better for M5225X?</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Which-HTTPd-is-better-for-M5225X/m-p/177550#M7057</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to complete the existing demo http web servers with necessary features: HTTP basic authentication, POST method and DHCP client. I evaluated MQX demo project, Niche + CMX demo, digibutler projects, FreeRTOS demo, uC/OS-II demo. According to my test result, the MQX demo has the most stable performance. So I hope to use MQX demo as code base, although Digibutler has implemented the authentication part. And I saw the authentication code is implemented in RTCS/MQX. However, the RTCS pdf in MQX is very comprehensive, but not too much on http server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know how to use the RTCS HTTP?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 02 May 2009 20:00:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Which-HTTPd-is-better-for-M5225X/m-p/177550#M7057</guid>
      <dc:creator>allankliu</dc:creator>
      <dc:date>2009-05-02T20:00:22Z</dc:date>
    </item>
    <item>
      <title>Re: Which HTTPd is better for M5225X?</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Which-HTTPd-is-better-for-M5225X/m-p/177551#M7058</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You may like to also look at the uTasker project (normally a M5225X is running on-line at &lt;A href="http://demo.uTasker.com" rel="nofollow" target="_blank"&gt;demo.uTasker.com&lt;/A&gt;). This includes HTTP with post (ARP, RARP, ICMP, IP, UDP, DHCP, DNS, TFTP, TCP, dynamic HTTP, FTP, SMTP, POP3, TELNET, NetBIOS and VLAN), with DHCP and much more...&lt;BR /&gt;&lt;A href="http://www.utasker.com/kirin3.html" rel="nofollow" target="_blank"&gt;http://www.utasker.com/kirin3.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 May 2009 03:51:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Which-HTTPd-is-better-for-M5225X/m-p/177551#M7058</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2009-05-03T03:51:50Z</dc:date>
    </item>
  </channel>
</rss>

