Re: [polyml] Non-blocking socket functions called without MSG_DONTWAIT flag

2019-06-20 Thread Kostirya
Thanks for clarifying.
Nick.

ср, 19 июн. 2019 г. в 21:31, David Matthews :
>
> If I've understood your question correctly the answer is that sockets
> are set to non-blocking mode when they are created so all operations are
> non-blocking.  Blocking operations are simulated by not returning to the
> caller until the operation has completed.  The reason for this is that
> it allows a thread to be interrupted or killed from within the run-time
> system.
>
> David
>
> On 19/06/2019 11:52, Kostirya wrote:
> > Hello.
> > I have question.
> > Why Non-blocking socket functions called without MSG_DONTWAIT flag?
> > Nick.
> > ___
> > polyml mailing list
> > polyml@inf.ed.ac.uk
> > http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
> >
> ___
> polyml mailing list
> polyml@inf.ed.ac.uk
> http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
___
polyml mailing list
polyml@inf.ed.ac.uk
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml

Re: [polyml] Non-blocking socket functions called without MSG_DONTWAIT flag

2019-06-19 Thread David Matthews
If I've understood your question correctly the answer is that sockets 
are set to non-blocking mode when they are created so all operations are 
non-blocking.  Blocking operations are simulated by not returning to the 
caller until the operation has completed.  The reason for this is that 
it allows a thread to be interrupted or killed from within the run-time 
system.


David

On 19/06/2019 11:52, Kostirya wrote:

Hello.
I have question.
Why Non-blocking socket functions called without MSG_DONTWAIT flag?
Nick.
___
polyml mailing list
polyml@inf.ed.ac.uk
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml


___
polyml mailing list
polyml@inf.ed.ac.uk
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml