Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > Python > Re: select.select and socket.setblocking

Reply
Thread Tools

Re: select.select and socket.setblocking

 
 
Jean-Paul Calderone
Guest
Posts: n/a
 
      12-30-2008
On Tue, 30 Dec 2008 15:55:51 -0500, Jean-Paul Calderone <(E-Mail Removed)> wrote:
>On Tue, 30 Dec 2008 14:41:17 -0600, Grant Edwards <(E-Mail Removed)> wrote:
>>On 2008-12-30, Francesco Bochicchio <(E-Mail Removed)> wrote:
>>>3. AFAIK (sorry, I feel acronym-ly today , there is no difference in
>>>select between blocking and non-blocking mode. The difference is in the
>>>recv (again, assuming that you use TCP as protocol, that is AF_INET,
>>>SOCK_STREAM), which in the blocking case would wait to receive all the
>>>bytes that you requested,

>>
>>No, in blocking mode it will wait to receive _some_ data (1 or
>>more bytes). The "requested" amount is strictly an upper
>>limit: recv won't return more than the requested number of
>>bytes, but it might return less.

>
>Hi Grant,
>
>I don't think you read Francesco's message carefully enough.


Ah, no, it was I who didn't read carefully enough. Nevermind.

Jean-Paul
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
if and and vs if and,and titi VHDL 4 03-11-2007 05:23 AM



Advertisments