From young@telebit.com Tue Feb  8 08:55:22 1994
Received: from apache.telebit.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA27728; Tue, 8 Feb 1994 19:56:35 -0500
Received: from america.Sunnyvale.Telebit.CO (america-bb.sunnyvale.telebit.com) by apache.telebit.com (4.1/SMI-4.1/Telebit-Apache-Brent-930718)
	id AA03487 to winsock-users@sunsite.unc.edu; Tue, 8 Feb 94 16:56:20 PST
Received: from napa.Sunnyvale.Telebit.COM by america.Sunnyvale.Telebit.COM (4.0/america.telebit.com-DBC-930718)
	id AA23833 to winsock-users@sunsite.unc.edu; Tue, 8 Feb 94 16:55:22 PST
Date: Tue, 8 Feb 94 16:55:22 PST
From: young@telebit.com (Dennis Young)
Message-Id: <9402090055.AA23833@america.Sunnyvale.Telebit.COM>
To: winsock-users@sunsite.unc.edu
Subject: is blocking select a bad idea?



  I am porting some Unix code to the MS Windows
  platform.  I have a few questions on what is
  the best way to incorporate the WinSock without
  making major modifications to the Unix IPC code.

  My main concern is on how to replace the BSD select.
  The simplest way is to replace it with WinSock's
  blocking select.  This select internally uses PeekMessage
  (according to the DefaultBlockingHook in section 4.3.13).
  However, the winsock document strongly discourages
  the use of blocking call.  Does this concern apply to the
  blocking select?  I would not think so because the 
  PeekMessage call yields control to other programs
  when message is available, right?

  Another approach is to use the WSAsyncSelect(), but
  this would entail too much modifications to the code.

  Any suggestion is greatly appreciated.

  Please respond to "young@telebit.com" direct or cc:,
  since I don't know whether my sign-up request to 
  winsock-request is working yet.

  Thank you very much.

    dennis
From slieb@morgan.com Tue Feb 15 09:36:31 1994
Received: from gateway.morgan.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA03615; Tue, 15 Feb 1994 14:36:54 -0500
Received: from mercnyw1.morgan.com ([138.20.145.12]) by gateway.morgan.com with SMTP id <41433>; Tue, 15 Feb 1994 14:36:45 -0500
Received: from bwit127.morgan.com by mercnyw1.morgan.com (5.65c/IDA-sendmail/cf.hub v1.24)
	id AA08340; Tue, 15 Feb 1994 14:36:33 -0500
Received: by bwit127.morgan.com (5.65c/IDA-sendmail/cf.host v1.23)
	id AA05649; Tue, 15 Feb 1994 14:36:32 -0500
From: slieb@morgan.com (Steve Lieblich)
Message-Id: <9402151436.ZM5647@is.morgan.com>
Date: 	Tue, 15 Feb 1994 14:36:31 -0500
X-Mailer: Z-Mail (2.1.3 10feb93)
To: winsock-users@sunsite.unc.edu
Subject: winsock questions

- How does one subscribe to this mail group?

- The most recent files found in /pub/micro/pc-stuff/ms-windows/...
    ../winsock/winsock-users-archive and winsock-hackers-archive
  are read protected and thus inaccessible for anonymous ftp.  Is
  this by design, and if so, is there an alternate site for these?
  If not, who should correct the permissions on these files?

- I am currently developing a winsock application using Novell's
  Lan Workplace stack.  I have designed the system to use the
  WSAAsyncSelect, and find under certain circumstances that my
  program does NOT get posted an FD_READ message when in fact the
  programs to which it connects are sending it data.  Has anyone
  had similar problems with this?

Thanks.

--steve lieblich
  slieb@morgan.com

From rysanek@arwen.ics.muni.cz Thu Feb 17 14:51:07 1994
Received: from aragorn.ics.muni.cz by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA04108; Thu, 17 Feb 1994 08:52:20 -0500
Received: from arwen.ics.muni.cz by aragorn.ics.muni.cz with SMTP id AA06116
  (5.67a8/IDA-1.4.4 for <winsock-users@calypso-2.oit.unc.edu>); Thu, 17 Feb 1994 14:52:08 +0100
Received: by arwen.ics.muni.cz id AA25437
  (5.67a/IDA-1.4.4 for winsock-users@sunsite.unc.edu); Thu, 17 Feb 1994 13:51:09 +0100
Message-Id: <199402171251.AA25437@arwen.ics.muni.cz>
Subject: Wint NT socket crash
To: winsock-users@sunsite.unc.edu (Windows Winsock )
Date: Thu, 17 Feb 1994 13:51:07 +0100 (MET)
From: Martin Rysanek <rysanek@arwen.ics.muni.cz>
X-Mailer: ELM [version 2.4 PL21]
Content-Type: text
Content-Length: 1104      

HI,
I have a problem with my Win NT AS. I'm about to write
a program which will send some stuffs to other machine using sockets.
But i have a still problem with closing of sockets.

If I close connection by closesocket(s), everything is OK.
If second computer close connection and i receive message
(lParam == 20, ....) and then I
WSAAsyncSelect(s, hWnd, 0, 0);
shutdown(s,2);
closesocket(s);
it means complete crash of WIN16 subsystem in WIN NT AS.

Then I cannot make logoff neither shutdown. It is neccessary 
to wait about 6 minut to recover Win NT AS and to make shutdown. 
I cannot continue in my work without complete restart of Win NT AS.      

I wrote my program with BC C++ 3.1 (Trumpet Beta release #5) 
and I have no problem in the Windows 3.1. When I relink
this program with Win NT AS winsock.lib and put it in
the Win NT AS it means crash of NT.

Any idea? 

Martin Rysanek
 
----------------------------------------------------
Martin Rysanek             Technical University Brno
Brno                       RYSANEK@DCSE.FEE.VUTBR.CZ
Czech Republic             RYSANEK@ARWEN.ICS.MUNI.CZ
From jimg@nsmdserv.cnd.hp.com Mon Feb 28 05:35:20 1994
Received: from hp.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA18818; Mon, 28 Feb 1994 14:35:23 -0500
Received: from nsmdserv.cnd.hp.com by hp.com with SMTP
	(1.36.108.7/15.5+IOS 3.13) id AA18428; Mon, 28 Feb 1994 11:35:21 -0800
Received: by nsmdserv.cnd.hp.com
	(1.37.109.8/15.5+ECS 3.3) id AA12329; Mon, 28 Feb 1994 12:35:20 -0700
From: jimg@nsmdserv.cnd.hp.com (Jim Greuel X2493)
Message-Id: <9402281235.ZM12327@nsmdserv.cnd.hp.com>
Date: Mon, 28 Feb 1994 12:35:20 -0700
X-Mailer: Z-Mail (2.1.2 11jan93)
To: winsock-users@sunsite.unc.edu
Subject: Local communications optimized?

Are there any winsock implementations which optimize local
communications (i.e., communications in which the "remote"
socket is actually on the local node) by using some local IPC
mechanism rather than sending the data down the networking
stack, ala Unix domain sockets?  

Thanks in advance,
Jim Greuel



-- 
Jim Greuel
Network and System Management Division		Hewlett-Packard
Email: j_greuel@hpcnd.cnd.hp.com		3404 E Harmony Rd.
Telephone: (303)229-2493 			Ft. Collins, CO  80525
Fax: (303)229-3526
