http://bugs.winehq.org/show_bug.cgi?id=17195 --- Comment #19 from Juan Lang <juan_lang(a)yahoo.com> 2009-02-11 12:19:08 --- (In reply to comment #16)
2) start off in non-message-mode and switch to message-mode with data still unread
As I expected, this isn't allowed, either on the client end or server end of a named pipe. My tests that demonstrate it were sent in: http://www.winehq.org/pipermail/wine-patches/2009-February/069264.html
3) start off in message-mode and switch to non-message-mode with data outstanding and not outstanding, as two separate tests.
This, in contrast, is possible. I haven't tested reading and writing in this case, just that the API to switch modes succeeds. See the above link.
4) do a CreateNamedPipe in message-mode on server-end and don't set message-mode on the client, and see what happens
Also possible.
5) do a CreateNamedPipe _not_ in message-mode on server-end, and set message-mode on the server, and see what happens.
Not possible. See tests. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.