On Tue, 30 Aug 2005, Vincent Snijders wrote:
> Michael Van Canneyt wrote:
> >
> > On Tue, 30 Aug 2005, Vincent Snijders wrote:
> >
> >
> >>Micha Nelissen wrote:
> >>
> >>>On Tue, 30 Aug 2005 11:09:30 +0200 (Romance Daylight Time)
> >>>Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
> >>>
> >>>
> >>>>In windows, it's slightly more difficult (surprise, surprise :-) )
> >>>>
> >>>>You can use MsgWaitForMultipleObjects to do this for a windows
> >>>>handle, or use WaitForSingleObject on a simple file handle.
> >>>
> >>>
> >>>You can't "wait" for file handles in windows.
> >>>
> >>
> >>AFAIK you can wait for file handles, but not for pipe handles.
> >
> >
> > You can wait on any handle: file, pipe, socket.
> >
> > From msdn:
> >
> > The WaitForSingleObject function can wait for the following objects:
> >
> > * Change notification
> > * Console input
> > * Event
> > * Job
> > * Memory resource notification
> > * Mutex
> > * Process
> > * Semaphore
> > * Thread
> > * Waitable timer
> >
> > The MsgWaitForMultipleObjects function can specify handles of any of the
> > following object types in the pHandles array:
> >
> > * Change notification
> > * Console input
> > * Event
> > * Job
> > * Memory resource notification
> > * Mutex
> > * Process
> > * Semaphore
> > * Thread
> > * Waitable timer
> >
>
> Didn't you notice "pipe" is missing in both lists? Or is pipe called
> differently?
Both pipes and TCP/IP sockets are missing in this list.
Michael.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
