-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does this library support read-only or write-only? #39
Comments
Currently the main pipe for creating connections and the additional pipes for the connections themselves use the same method, so this is not possible for the main client (but will most likely work with SingleConnection versions of clients) |
I added |
PipeServer.CreatePipeStreamForConnectionFunc No effect PipeConnection has a reading thread. If it is set to write only, ReadAsync will prompt that reading is not supported. |
I created test for WriteOnly server case and disabled reading thread if PipeStream does not have Read capabilities. It should be released soon in 2.1.0. |
Looking forward to the release of the new version.😊 |
Unfortunately, I'm running macOS and it worked correctly, but the Windows tests failed with an exception and I'm trying to fix it:
|
Hi, have you found your problem? |
Unfortunately stuck with this. I will release a new prerelease version with the ability to set CreatePipeStreamForConnectionFunc for the client, you can help if you check different options |
I roughly looked at the PipeConnection code, and there is a start method. If the NamedPipeClientStream is in the write-only state, I think PipeConnection.ReadWorker does not need to be run. |
After testing the 2.1.0-dev322 version, it seems that it can only read and write. Close this issue. |
CreatePipeStreamFunc = (pipeName) => new NamedPipeServerStream(pipeName, PipeDirection.Out, 1, PipeTransmissionMode.Byte, PipeOptions.Asynchronous | PipeOptions.WriteThrough);
When customizing a NamedPipeServerStream, the client connects and prompts that reading the stream is not supported.
The text was updated successfully, but these errors were encountered: