Unlike *nix, named pipes in Windows are not visible in a regular directory. But print(os.listdir(r'\\.\pipe')) does show a list of what are apparently pipe names, including the one I expect to return my data from the app to wsgi.
On Tuesday, August 15, 2017 at 3:26:29 PM UTC-7, mickeyf wrote: > > I am trying to communicate with a Windows 7 .NET 3..5 C# app from wsgi and > Apache 2.4. I have successfully sent posted data to the C# app using named > pipes, but when I even try to open or access a pipe in the python wsgi > code, it fails, usually with "an operation was attempted on something that > is not a socket" . > > I have had success (in one direction) both with > win32pipe.CreateNamedPipe(r'\\.\pipe\pipe_from_myapp' .. etc) > and with > open(r'\\.\pipe\pipe_from_myapp', 'r+b', 0) > > When testing the same code in a test script that was not wsgi, I was able > to pass messages in both directions. I have generally used separate pipes, > one for sending and one for receiving. > > I speculate that my problem may be a permissions issue, but I'm not sure > where to look. httpd is running (for test purposes) "as Administrator" - > from the command line, not as a deamon. I am also looking into whether the > pipe may be closed at the wsgi end before the response has had a chance to > arrive. > > Any clues or suggestions are appreciated, or if anyone has successfully > sent messages to and from C# and has a working formula, I'd love to hear > about it. > > Thanks > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
