Message150716
| Author |
neologix |
| Recipients |
BreamoreBoy, gearb0x, jnoller, neologix, news1234, pitrou |
| Date |
2012年01月06日.08:19:21 |
| SpamBayes Score |
4.436283e-07 |
| Marked as misclassified |
No |
| Message-id |
<CAH_1eM2XBsGC16uB9VG4aRx=ZpT49Hcq-vc-+PyCNveir7C+Qw@mail.gmail.com> |
| In-reply-to |
<1325816333.91.0.969165023049.issue8184@psf.upfronthosting.co.za> |
| Content |
> Like I said, I dont know much about named pipes and im not even sure thats how they are intended to work in this context. IE: if one process is listening, can another listen on that named pipe as well?
Under Unix, you'd get a EADDRINUSE with a Unix domain socket.
I don't know much about Windows, but here's what CreateNamedPipe doc says:
"""
FILE_FLAG_FIRST_PIPE_INSTANCE
0x00080000
If you attempt to create multiple instances of a pipe with this flag,
creation of the first instance succeeds, but creation of the next
instance fails with ERROR_ACCESS_DENIED.
Windows 2000: This flag is not supported until Windows 2000 SP2 and Windows XP.
"""
So it seems that we should probably pass FILE_FLAG_FIRST_PIPE_INSTANCE
under Windows. |
|