Query in Sockets

"Bhuvaneswari R.P" <bhuvanarp@future.futsoft.com> Thu, 21 March 2002 08:56 UTC

Reply-To: <bhuvanarp@future.futsoft.com>
From: "Bhuvaneswari R.P" <bhuvanarp@future.futsoft.com>
To: <tcp-impl@grc.nasa.gov>
Subject: Query in Sockets
Date: Thu, 21 Mar 2002 14:26:37 +0530
Message-Id: <002401c1d0b6$50203d80$1606140a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
In-Reply-To: <001f01c1c442$e14ba040$1606140a@future.futsoft.com>
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0025_01C1D0E4.69D87980"
Sender: owner-tcp-impl@grc.nasa.gov
Precedence: bulk
Status: RO
Content-Length: 4268
Lines: 105

Hello,

I have a doubt in sockets. I don't know whether this is the right mailing list
for posting my query.

When I create a socket, the socket will be in Blocking mode.
The socket can be set to Non-Blocking mode using the call 'fcntl'.

Is there some mechanism by which a socket already in Non-Blocking mode,
can be set to Blocking mode.

If this is not the right mailing list, it would be very helpful if someone let's
me know the mailing list
where I can post my queries with respect to sockets.

-Regards,
Bhuvaneswari.

***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information 
and should not be circulated or used for any purpose other than for 
what it is intended. 

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. 
FSL accepts no responsibility for loss or damage arising from 
the use of the information transmitted by this email including
damage from virus.
***************************************************************************