[En-Nut-Discussion] NutTcpAccept blocks the tread

Michael Smola Michael.Smola at gmx.net
Thu Oct 22 17:38:09 CEST 2009



----- Ursprüngliche Nachricht -----
Von: Bernd Walter <enut at cicely.de>
Gesendet: Donnerstag, 22. Oktober 2009 01:34
An: Ethernut User Chat (English) <en-nut-discussion at egnite.de>
Betreff: Re: [En-Nut-Discussion] NutTcpAccept blocks the tread

On Wed, Oct 21, 2009 at 02:31:08PM -0700, urbi wrote:
> 
> 
> Ethernut wrote:
> > 
> >>Unfortunately Urban's request wasn't that specific: "...so I have to
> >>spend for each connection his own thread." This would be true for
> >>Berkeley/Posix sockets as well. Btw. dynamically creating threads on
> >>incoming connections is shown in the current app/httpd sample.
> > 
> >>Urban, can you please specify in more detail, what you are expecting?
> > 
> 
> Ok. I will try to explaine wath I want to have. I use only in one project an
> operating sytem. On other projects I am programming with event driven state
> machins. The synchronisation for these state machins is implemented in the
> main-loop. In such systems It is importend to have non blocking functions


More information about the En-Nut-Discussion mailing list