<?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>topic Re: Multiple sockets, same port in ColdFire/68K Microcontrollers and Processors</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Multiple-sockets-same-port/m-p/145421#M3097</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Thanks Mark!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;I pretty much got through it by the end of the day yesterday, but you have confirmed what I did. I have done this kind of thing many times using standard Berkeley sockets, but between their added twist of having to use a callback routine for everything and and the examples using their "msring" ring buffer code, I was thoroughly confused.I needed more control over the buffer assignments so I ended writing a special version of some of the msring functions and then took more control in my app.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Bob&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Feb 2007 21:12:21 GMT</pubDate>
    <dc:creator>tobiasplayer</dc:creator>
    <dc:date>2007-02-21T21:12:21Z</dc:date>
    <item>
      <title>Multiple sockets, same port</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Multiple-sockets-same-port/m-p/145419#M3095</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hi,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&amp;nbsp;What is the proper method for opening several passive sockets listening on the same port with the mini-sockets API. Do I start one listen socket and try to spawn the connections from that or do I need to open a different listen socket for every connection I wish to allow?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks,&lt;/DIV&gt;&lt;DIV&gt;Bob&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Feb 2007 21:51:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Multiple-sockets-same-port/m-p/145419#M3095</guid>
      <dc:creator>tobiasplayer</dc:creator>
      <dc:date>2007-02-19T21:51:02Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple sockets, same port</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Multiple-sockets-same-port/m-p/145420#M3096</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hi Bob&lt;BR /&gt;&lt;BR /&gt;Essentially it is only possible to have one listener on a particulat port.&lt;BR /&gt;&lt;BR /&gt;Generally the listener then checks the source port to see whether there is already a connection. If not, it needs to 'create' a new connection (probably spawn in your terminology) to which it assigns the source port as reference.&lt;BR /&gt;Further frames to the particular open connection are then handled by the session (thread or whatever) assigned to the source port.&lt;BR /&gt;When the connection terminates, the connection resources can be freed.&lt;BR /&gt;&lt;BR /&gt;The system must be dimensioned to be able to handle the expected number of parallel connections expected to be encountered. If a new connection is not possible since the connection limit has been reached the connection can be refused by sending a RST.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.uTasker.com" rel="nofollow" target="_blank"&gt;&lt;IMG src="http://www.uTasker.com/uTaskerLogoSS.jpg" /&gt;&lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Feb 2007 20:54:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Multiple-sockets-same-port/m-p/145420#M3096</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2007-02-21T20:54:11Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple sockets, same port</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Multiple-sockets-same-port/m-p/145421#M3097</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Thanks Mark!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;I pretty much got through it by the end of the day yesterday, but you have confirmed what I did. I have done this kind of thing many times using standard Berkeley sockets, but between their added twist of having to use a callback routine for everything and and the examples using their "msring" ring buffer code, I was thoroughly confused.I needed more control over the buffer assignments so I ended writing a special version of some of the msring functions and then took more control in my app.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Bob&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Feb 2007 21:12:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Multiple-sockets-same-port/m-p/145421#M3097</guid>
      <dc:creator>tobiasplayer</dc:creator>
      <dc:date>2007-02-21T21:12:21Z</dc:date>
    </item>
  </channel>
</rss>

