On Mon, Jun 11, 2001 at 12:30:59PM -0500, William A. Rowe, Jr. wrote: > From: <[EMAIL PROTECTED]> > Sent: Monday, June 11, 2001 10:58 AM > > > > > Which is also a requirement. When we call namedpipe_create, we have to > > > RETURN > > > SOMETHING! Win32 will create a pipe handle (not the same as the > > > read/write file > > > handle.) Every (NT/2000) machine could Create or Connect to get that > > > pipe handle. > > > But once that pipe handle is closed, the pipe evaporates, they are not > > > persistant.
is there anybody out there who really understands, or has used, pipes on NT? CreateIoCompletionPort! that's the one!!! dammit, not WaitNamedPipeHandleState, what am i talking about. okay, just looking at the online MSDN on ms's site, the function i am referring to that is somewhat equivalent to listen/accept, esp. for use in multi-threaded code, is CreateIoComplationPort. i could be wrong: it may be possible to just use the message-based functions CallNamedPipe, TransactNamedPipe etc. help, help, who really 'gets' this stuff? [i understand what it looks like over-the-wire when this stuff happens over SMB, but have no connection back to the Win32 APIs that *generate* that network traffic!] luke
