2 Attachment(s)
Re: How to Write a program to communicate between two processes using the pipe.
Quote:
...why would you want to rewrite it from using unicode to multibyte ?
For the obvious reason that just one line of code in the Pipe Client class needed to be changed, whereas the project I plan to use this methodology in has hundreds of lines of code that would need to be changed. To that point, I am slowly and painfully rewriting the target project to be Unicode compliant, but that is another topic.
As far as DACL being set to NULL, that is a very good point. But I don't think it would matter in this test project that is run on the same machine with administrative privileges (or am I wrong about that).
In support of that view:
Quote:
lpSecurityDescriptor
A pointer to a SECURITY_DESCRIPTOR structure that controls access to the object.
If the value of this member is NULL, the object is assigned the default security
descriptor associated with the access token of the calling process. This is not
the same as granting access to everyone by assigning a NULL discretionary access
control list (DACL). By default, the default DACL in the access token of a process
allows access only to the user represented by the access token.
see: http:msdn.microsoft.com/en-us/library/windows/desktop/aa379560(v=vs.85).aspx
In any case, it will be an easy task to rewrite this small test project in Unicode, but I strongly suspect the result will be the same because I don't think that is the problem. To verify that impression, I have attached UTF-16 versions of the Named Pipe demos with and without an associated dll.
