Re: Testing if a Socket is Blocked or Non-Blocked

Scott,
thank you again for all of you help.
I have determined that the issue I was attempting to solve was due to my
program issuing an accept() function to wait for a connection instead of
the nbaccept() which would create the socket as non-blocked.

Thanks to you and all of the others who have responded to my questions
regarding socket processing, I have a better understanding of how the
process works.

Jeff Young
Sr. Programmer Analyst

On Sat, Sep 26, 2015 at 4:38 AM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
wrote:

If a socket is already in non-blocking mode, setting it to non-blocking
again won't hurt anything.


On 9/25/2015 8:25 AM, Jeff Young wrote:

Scott,
In my program, I am issuing a number of reads to the socket, and while I
have set the socket to Non-Block, someone else calling the nbrecv
procedure
may not do so, and end up in a wait on the first recv() if the socket is
not Non-Blocked.
Is there any down side to forcing the socket to be Non-Blocked if it is
already Non-Blocked?

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.