problem with CSocket and timers

caedmon irias -- caedmoni@ix.netcom.com
Tuesday, January 28, 1997

Environment: VC++4.2-flat, Windows 95

I have an application that is using a CSocket as well as a timer.  The
problem is, the Connect call never returns.  The connection is accepted by
the server, but CSocket seems to be totally confused by the timer messages
and never figures out that it's connected.  If I simply don't set the
timer, the socket works fine.  Is there something I'm doing wrong here or
is this just a 'feature' of CSocket? 

---

Mike Blaszczak -- mikeblas@nwlink.com
Wednesday, January 29, 1997

[Mini-digest: 3 responses]

At 08:40 1/28/97 -0800, caedmon irias wrote:
>Environment: VC++4.2-flat, Windows 95

MFC 4.2-flat only works with certain beta-versions of operating system
components.  Now that those components have been released in their final
form, it is imperative that you upgrade your copy of MFC to 4.2b by
installing the readily available patch.

>I have an application that is using a CSocket as well as a timer.  The
>problem is, the Connect call never returns.  The connection is accepted by
>the server, but CSocket seems to be totally confused by the timer messages
>and never figures out that it's connected.  If I simply don't set the
>timer, the socket works fine.  Is there something I'm doing wrong here or
>is this just a 'feature' of CSocket? 

Some pretty wierd interactions between timers and sockets were fixed in
the 4.2b patch.  Too bad you haven't installed it, huh?

After that, there was a really rare race condition that would cause a hang
when a socket was closing and a timer fired at exactly the same time.  That
was fixed for the next version.


.B ekiM
http://www.nwlink.com/~mikeblas/
These words are my own. I do not speak on behalf of Microsoft.
           This performance was not lip-synched.

-----From: John Young 

Hi Caedmon,

At 08:40 am 28/1/97 -0800, caedmon irias wrote:
>Environment: VC++4.2-flat, Windows 95
>
>I have an application that is using a CSocket as well as a timer.  The
>problem is, the Connect call never returns.  The connection is accepted by
>the server, but CSocket seems to be totally confused by the timer messages
>and never figures out that it's connected.  If I simply don't set the
>timer, the socket works fine.  Is there something I'm doing wrong here or
>is this just a 'feature' of CSocket? 

Have a look at KB article Q138692 "How to Configure a Time-Out on a CSocket
Operation", which may point you in the right direction.

-John


John Young, Yaesu Musen Co., Ltd., Japan.
If only computers did what you wanted, not what you tell them.

-----From: jlo@nera.no (Jan Lonsetteig)

       Upgrade to VC++4.2b. This is a bug in 4.2.

       /Jan Lonsetteig





       mfc-l @ netcom.com AT Internet@NeraOslo
       97-01-28 08:40

       To:   mfc-l @ netcom.com AT Internet@NeraOslo
       cc:    (bcc: Jan Lonsetteig/SATCOM/NORWAY/NERA)
       Subject:  problem with CSocket and timers


 Environment: VC++4.2-flat, Windows 95

 I have an application that is using a CSocket as well as a timer.
 The problem is, the Connect call never returns.  The connection is
 accepted by the server, but CSocket seems to be totally confused by
 the timer messages and never figures out that it's connected.  If I
 simply don't set the timer, the socket works fine.  Is there
 something I'm doing wrong here or is this just a 'feature' of
 CSocket?

---

| Вернуться в корень Архива |